-
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
[JSWSERVER-14389] Navigate from JIRA to branch or pull request
Workflow | Original: JAC Suggestion Workflow [ 3069173 ] | New: JAC Suggestion Workflow 3 [ 3659258 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: Confluence Workflow - Public Facing v4 [ 2626198 ] | New: JAC Suggestion Workflow [ 3069173 ] |
Workflow | Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2322359 ] | New: Confluence Workflow - Public Facing v4 [ 2626198 ] |
Status | Original: Closed [ 6 ] | New: Resolved [ 5 ] |
Workflow | Original: JIRA PM Feature Request Workflow v2 [ 2041510 ] | New: JIRA PM Feature Request Workflow v2 - TEMP [ 2322359 ] |
Workflow | Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2029651 ] | New: JIRA PM Feature Request Workflow v2 [ 2041510 ] |
Workflow | Original: JIRA PM Feature Request Workflow v2 [ 1553791 ] | New: JIRA PM Feature Request Workflow v2 - TEMP [ 2029651 ] |
Component/s | New: DVCS Accounts [ 43316 ] | |
Labels | New: migrated_from_dcon |
Key |
Original:
|
New:
|
Workflow | Original: classic workflow for JIRA DVCS Connector [ 689231 ] | New: JIRA PM Feature Request Workflow v2 [ 1553791 ] |
Issue Type | Original: New Feature [ 2 ] | New: Suggestion [ 10000 ] |
Priority | Original: Minor [ 4 ] | |
Project | Original: DCON - deprecated use JSW [ 14710 ] | New: JIRA Software (including JIRA Agile) [ 12200 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: classic default workflow [ 552047 ] | New: classic workflow for JIRA DVCS Connector [ 689231 ] |
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.