-
Suggestion
-
Resolution: Fixed
-
None
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
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-14389] Navigate from JIRA to branch or pull request
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? 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. 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
Will this be made available to show pull requests from GitHub into JIRA Development Panel in OnDemand?
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. 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".
Lars Janssen
added a comment - Very useful, thanks!
There is something that looks like a small bug, but might just be confusing. For one issue it says:
"1 pull request" and then a status "open".
But when I click this, it opens up and shows 4 pull requests. This is correct, there are 4 PRs. But 3 of them are merged, and 1 is open. So, it looks like there is only 1 PR in total.
Lars Janssen
added a comment - Very useful, thanks!
There is something that looks like a small bug, but might just be confusing. For one issue it says:
"1 pull request" and then a status "open".
But when I click this, it opens up and shows 4 pull requests. This is correct, there are 4 PRs. But 3 of them are merged, and 1 is open. So, it looks like there is only 1 PR in total. 
Olly
added a comment - Looks great to me. Thank you. 
Learnship
added a comment - From our end, this is perfect! Thanks! Guys, could you check out the new Devleopment panel in JIRA 6.2 and see if it satisfies all your needs raised in this issue? 
Administrator's guide is here
Matthew Hillier
added a comment - +2 (from me and by Release Manager). It's not a show stopper, but as a quality-of-life improvement this would really help us so that non-development staff can get a quicker overview of what's going on in Bitbucket!
Matthew Hillier
added a comment - +2 (from me and by Release Manager). It's not a show stopper, but as a quality-of-life improvement this would really help us so that non-development staff can get a quicker overview of what's going on in Bitbucket! Lars Janssen
added a comment - +1 to @Learnship's point about turning into a link to the branch.
Also, it would be really useful to see a clear link to the corresponding pull request(s)* (not just hidden away in one of the tabs, but in all views).
(* - there's probably one PR in most cases, but not always)
Lars Janssen
added a comment - +1 to @Learnship's point about turning into a link to the branch.
Also, it would be really useful to see a clear link to the corresponding pull request(s)* (not just hidden away in one of the tabs, but in all views).
(* - there's probably one PR in most cases, but not always) 
Paul O'Flynn
added a comment - As long as we're talking onDemand Jira and BitBucket with Git I am all for it!!
Paul O'Flynn
added a comment - As long as we're talking onDemand Jira and BitBucket with Git I am all for it!! Learnship
added a comment - This would be especially useful as now there is a "Development" section on a JIRA ticket with a "Create Branch" link, which unfortunately does not turn into a link to a branch once used, causing confusion whether there already is a branch with the ticket # or not.
Learnship
added a comment - This would be especially useful as now there is a "Development" section on a JIRA ticket with a "Create Branch" link, which unfortunately does not turn into a link to a branch once used, causing confusion whether there already is a branch with the ticket # or not. 
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-393is not relevant.DCON-393only 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.