-
Suggestion
-
Resolution: Unresolved
-
11
-
8
-
As a developer, I would like to be able to associate any BitBucket branch with one or more Jira tickets. I cannot do this at this time because the branch name must include the ticket's key.
It would be great if I could associate any branch, regardless of the branch's name with any Jira ticket(s).
- is duplicated by
-
- Gathering Interest
- relates to
-
- Closed
[JSWCLOUD-18105] Allow linking a BitBucket branch with a Jira ticket without having to include the ticket key in the branch name.
Just been forced to move from azure devops to BB - like going back in time... It's just a link to the branch in git, you can have one ticket and many branches that resolve that ticket (UI, API, infrastructure) Maybe the devs that work on BB don't actually have to use it? Oh and don't get me started on the lack of dark mode...
ery helpful. It's easy to forget to look at the Jira issue key when creating the branch, and I don't want to have to remember to create the branch from Jira instead of just creating locally, then pushing the branch which is much more natural.
I would love if we could use the 'Labels' feature to be able to reference the Jira ticket and then have Jira just pick that up. Then multiple branches which have resolutions to multiple tickets could be used.
This feature is absolutely needed. In my workflow branch is created with a milestone name and almost always does not map to a single issue. We fudge it by creating Epic issues to match the branch name but this in itself creates additional challenges. There must be a clean way in Jira to just link ANY commit without need to use the Jira issue key in the commit name. Please put some priority into this and thank you. Peace.
I'm an intern and this is part of my project requirements help Jira devs I don't wana get fired
Please add it!
Either that or make renaming of branches via the Bitbucket UI easier in order for us to retrospectively include the issue key in the name ☝️
+1