-
Suggestion
-
Resolution: Unresolved
-
None
-
79
-
1
-
The Problem
Not all workflows start with an issue. And not all issues have just one branch addressing them. Finally, not all branches address only one issue. However, the only way to correctly connect an issue and a branch is by creating a new branch from an issue. Meanwhile, this often not how issues are addressed.
Suggested Solution
Add a way to connect any existing issue with any existing branch in any connected VCS, regardless of creation order or name.
Remarks
There is already a [question|https://community.atlassian.com/t5/Jira-questions/How-to-link-existing-JIRA-issue-to-a-existing-branch-in/qaq-p/701496] about this in the Community website. A lot of people would like this implemented.
- duplicates
-
JSWCLOUD-18105 Allow linking a BitBucket branch with a Jira ticket without having to include the ticket key in the branch name.
- Gathering Interest
- is related to
-
BCLOUD-9470 Add ability to link previous commits to existing JIRA issues (BB-10211)
- Closed
- relates to
-
JRACLOUD-86777 Provide greater flexibility to auto-link JIRA Issues to source control commits
- Gathering Interest
- was cloned as
-
JRASERVER-70742 Ability to Link an Existing Issue to Any Existing Branch
- Gathering Interest
+1