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

Navigate from JIRA to branch or pull request

XMLWordPrintable

    • 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.

      Provide a way to navigate from a JIRA issue to a corresponding branch or pull request in Bitbucket or GitHub. I see that I can navigate to individual commits. I'm looking for the best way to navigate to the aggregate changes of all the commits corresponding to a JIRA issue.

      From this answers post: https://answers.atlassian.com/questions/202861/navigate-from-jira-to-branch-or-pull-request-in-bitbucket-or-github?page=1#202933

            [JSWSERVER-14389] Navigate from JIRA to branch or pull request

            ZehuaA added a comment -

            jgearheart which download version of JIRA are you using at the moment? If you have JIRA 6.2.1 or 6.2.2, I believe DCON-393 is not relevant. DCON-393 only affects JIRA OnDemand.
            If you still could not see PR on 6.2.1 or 6.2.2, please raise a separate support issue and we will investigate it.

            ZehuaA added a comment - jgearheart which download version of JIRA are you using at the moment? If you have JIRA 6.2.1 or 6.2.2, I believe DCON-393 is not relevant. DCON-393 only affects JIRA OnDemand. If you still could not see PR on 6.2.1 or 6.2.2, please raise a separate support issue and we will investigate it.

            Jason Gearheart added a comment -

            Is this fix in JIRA or the plugin? When will it be available for download users?

            Jason Gearheart added a comment - Is this fix in JIRA or the plugin? When will it be available for download users?

            ZehuaA added a comment -

            Yes, ted5. The fix for DCON-393 is scheduled to be deployed to OD tomorrow.

            ZehuaA added a comment - Yes, ted5 . The fix for DCON-393 is scheduled to be deployed to OD tomorrow.

            Ted Tencza added a comment -

            GitHub pull requests not showing in OnDemand is a bug - https://jira.atlassian.com/browse/DCON-393

            Ted Tencza added a comment - GitHub pull requests not showing in OnDemand is a bug - https://jira.atlassian.com/browse/DCON-393

            Jason Gearheart added a comment -

            GitHub pull requests are still not being displayed in the development panel. It is picking up branches and commits, but not pull requests.

            Jason Gearheart added a comment - GitHub pull requests are still not being displayed in the development panel. It is picking up branches and commits, but not pull requests.

            M (Inactive) added a comment -

            Yes, pull requests from GitHub are displayed in the development panel under three conditions:

            1. When the related branch has the issue key in the name
            2. When there is an included commit that has the issue key in the commit message
            3. When the pull request has an issue key in the title

            M (Inactive) added a comment - Yes, pull requests from GitHub are displayed in the development panel under three conditions: When the related branch has the issue key in the name When there is an included commit that has the issue key in the commit message When the pull request has an issue key in the title

            Ted Tencza added a comment - - edited

            Will this be made available to show pull requests from GitHub into JIRA Development Panel in OnDemand?

            Ted Tencza added a comment - - edited Will this be made available to show pull requests from GitHub into JIRA Development Panel in OnDemand?

            M (Inactive) added a comment -

            Thanks for the feedback everyone. I'm marking this as resolved since the new development panel in JIRA 6.2 seems to satisfy this issue.

            Cheers,

            Megan Cook
            Atlassian Product Manager

            M (Inactive) added a comment - Thanks for the feedback everyone. I'm marking this as resolved since the new development panel in JIRA 6.2 seems to satisfy this issue. Cheers, Megan Cook Atlassian Product Manager

            Lars Janssen added a comment -

            Thanks for explaining. I think if you try to show everything ("4 PRs, 1 open"), then there is too much on screen. So it's ok.

            Lars Janssen added a comment - Thanks for explaining. I think if you try to show everything ("4 PRs, 1 open"), then there is too much on screen. So it's ok.

            ZehuaA added a comment -

            lars.janssen Thanks for the feedback. I think that's a deliberate design decision. We've iterated the design a few times and ended up with the current one. It's more about emphasizing what needs to be actioned upon. I believe once you merge the fourth PR, it would show "4 pull requests MERGED".

            ZehuaA added a comment - lars.janssen Thanks for the feedback. I think that's a deliberate design decision. We've iterated the design a few times and ended up with the current one. It's more about emphasizing what needs to be actioned upon. I believe once you merge the fourth PR, it would show "4 pull requests MERGED".

              Unassigned Unassigned
              matt.mcclure Matt McClure
              Votes:
              27 Vote for this issue
              Watchers:
              21 Start watching this issue

                Created:
                Updated:
                Resolved: