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

Pull requests wrongly associated with issues

XMLWordPrintable

    • 1
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Software Server. Using JIRA Software Cloud? See the corresponding suggestion.

      Hi,

      Recently, during a release procedure, I came across behaviour that seems erroneous. Here's what I did, as far as I can remember:

      1. I had 3 issues with 3 BitBucket pull requests associated with them, visible through the Development panel on the Issue page.
      2. I accepted the pull requests into the develop branch. The Version page showed no warnings, as no issue was under review any longer.
      3. I created another pull request to merge develop into master. BitBucket detected the issues as being associated with the pull request.
      4. The Version page showed 3 warnings, saying that there are unmerged pull requests.

      At this point, hovering over "Under Review" for each issue on the Version page showed a popup stating that there is 1 pull request. Clicking "Under Review" reveals 2 pull requests, one of which is the original pull request for the issue, and the other one is the one from develop into master. On the Issue page for any of the 3 issues, similar behaviour could be observed: the "Development" panel shows 1 pull request with status "Open". Clicking it reveals 2 pull requests, one of which is the develop -> master pull request with status "Open" and the other one is the original issue pull request with status "Merged".

        1. pull-request-issue-img1.PNG
          pull-request-issue-img1.PNG
          46 kB
        2. pull-request-issue-img2.PNG
          pull-request-issue-img2.PNG
          41 kB
        3. pull-request-issue-img3.PNG
          pull-request-issue-img3.PNG
          6 kB

          Form Name

            [JSWSERVER-14942] Pull requests wrongly associated with issues

            Gosia Kowalska added a comment -
            Atlassian Update – 27 March 2018

            Hi,

            Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Sometimes potentially valuable tickets do get closed where the Summary or Description has not caught the attention of the community. If you feel that this suggestion is valuable, consider describing in more detail or outlining how this request will help you achieve your goals. We may then be able to provide better guidance.

            For more context, check out our Community blog on our renewed approach to highly voted Server suggestions for Jira and Confluence.

            Thanks again.
            Regards,
            Jira Product Management

            Gosia Kowalska added a comment - Atlassian Update – 27 March 2018 Hi, Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Sometimes potentially valuable tickets do get closed where the Summary or Description has not caught the attention of the community. If you feel that this suggestion is valuable, consider describing in more detail or outlining how this request will help you achieve your goals. We may then be able to provide better guidance. For more context, check out our Community blog on our renewed approach to highly voted Server suggestions for Jira and Confluence . Thanks again. Regards, Jira Product Management

              Unassigned Unassigned
              ec2e71b9b0b7 Anton Ukhanev
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: