Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-21243

DVCS syncing GitLab Pull Requests is not updating

XMLWordPrintable

      Issue Summary

      See details on gitlab issue tracker 

      Jira Development Panel Pull Request info is not updated when Jira issue key is in commit message

      This is happening in Gitlab 13.5.4, Jira self hosted 8.5.3 and the Jira DVCS Connector plugin 5.2.6.

      Steps to Reproduce

      Create a merge request where the Jira issue key only exists in commit messages, not the MR title or branch name.

      Expected Results

      According to Referencing issues in your development work the development panel Pull Request information should be updated when you do one of:

      • Include a commit in the pull request that has the issue key in the commit message. Note, the commit cannot be a merge commit.
      • Include the issue key in the pull request title.
      • Ensure that the source branch name includes the issue key.

      However, if you only include the issue key in the commit message the Development Panel Pull Request info is not updated. The Commits info is updated correctly.

      Actual Results

      The Jira development panel Pull Request info is not updated for the Jiras referenced in the commit messages.

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

            [JSWSERVER-21243] DVCS syncing GitLab Pull Requests is not updating

            Rinish made changes -
            Remote Link Original: This issue links to "THOR-328 (Bulldog)" [ 710824 ] New: This issue links to "THOR-328 (JIRA Server (Bulldog))" [ 710824 ]
            awojtasik made changes -
            Fix Version/s Original: 9.4.0 [ 102404 ]
            Fix Version/s New: 9.4.6 [ 104662 ]
            Lyuboslav Varbanov (Inactive) made changes -
            Fix Version/s New: 8.20.0 [ 95694 ]
            Fix Version/s New: 9.4.0 [ 102404 ]

            Asset Management added a comment -

            Looks like they fixed a similar issue in 8.20.17, but I'm not sure it's directly tied to our issue here: 
            JSWSERVER-21370 Duplicate values in AO_E8B6CC_COMMIT leads to DVCS MessageConsumer failure.
             
            That issue lists 8.20.17 and 9.5.0 as the fixes, nothing in 9.4.x.
             
            Guess we'll wait and see what is in 9.4.3 and 8.20.18.

            Asset Management added a comment - Looks like they fixed a similar issue in 8.20.17, but I'm not sure it's directly tied to our issue here:  JSWSERVER-21370 Duplicate values in AO_E8B6CC_COMMIT leads to DVCS MessageConsumer failure.   That issue lists 8.20.17 and 9.5.0 as the fixes, nothing in 9.4.x.   Guess we'll wait and see what is in 9.4.3 and 8.20.18.

            Asset Management added a comment -

            All,

            I have a response (whether this means Jira 9.4.2 or a yet-unreleased 9.4.3, likewise with 8.20.x, I don't know yet):

            We apologize for the delay on this request. We have just received confirmation from the Jira Dev team that the bug fix was backported to 8.20.x and 9.4.x versions of Jira as well. 

            The bug report Fix Version will be updated to match this information.

            We hope to have addressed your questions. Please let us know in case there's any other information we could provide on this matter.

            Regards,
            Atlassian Support Engineer

            Asset Management added a comment - All, I have a response (whether this means Jira 9.4.2 or a yet-unreleased 9.4.3, likewise with 8.20.x, I don't know yet): We apologize for the delay on this request. We have just received confirmation from the Jira Dev team that the bug fix was backported to 8.20.x and 9.4.x versions of Jira as well.   The bug report Fix Version will be updated to match this information. We hope to have addressed your questions. Please let us know in case there's any other information we could provide on this matter. Regards, Atlassian Support Engineer

            Asset Management added a comment -

            I have a support ticket to Atlassian to confirm if this is being backported to the LTS lines (Jira 9.4.x and 8.20.x) right now it just shows, at least here, fixed in 9.5.x

            Asset Management added a comment - I have a support ticket to Atlassian to confirm if this is being backported to the LTS lines (Jira 9.4.x and 8.20.x) right now it just shows, at least here, fixed in 9.5.x
            mandreiev (Inactive) made changes -
            Fix Version/s Original: 9.6.0 [ 104017 ]
            mandreiev (Inactive) made changes -
            Fix Version/s New: 9.6.0 [ 104017 ]

            asoiron added a comment -

            Hi, I see that this issue was closed. Does it mean the bug is fixed?

            asoiron added a comment - Hi, I see that this issue was closed. Does it mean the bug is fixed?
            SET Analytics Bot made changes -
            UIS Original: 71 New: 70

              cbf119536079 Lyuboslav Varbanov (Inactive)
              rarmstrong@atlassian.com Rory Armstrong (Inactive)
              Affected customers:
              10 This affects my team
              Watchers:
              25 Start watching this issue

                Created:
                Updated:
                Resolved: