Default branch name prefix from JIRA (BB-9390)

Issue #8216 duplicate
Ben Tatham
created an issue

When pushing "Create Branch" button on a JIRA Issue, it would be nice to configure the branch name to have a default prefix (like features/ as per gitflow). I imagine this feature would be a configuration open in BitBucket, not JIRA either way would be fine.

It should also use the configured "main branch" of the repo for "Branch from".

(I recall seeing something like at the Summit 2013, but perhaps that was on Stash instead.)

Official response

  • Aneita Yang staff

    Hi everyone,

    Thanks for your feedback on this ticket. Issue #12833 is another open ticket that is tracking this request. As that ticket has more votes and comments, I will update #12833 to include the main use cases that are mentioned on this ticket and mark this ticket as a duplicate.

    I encourage you to vote for and watch issue #12833 if it is something that you're interested in seeing as we regularly review the top voted issues for Bitbucket and provide updates on the ticket. Please feel free to also comment on that issue with any use cases that are not already covered.

    As mentioned on #12833, this request is not something that we will be addressing anytime soon as we're working on higher priority projects at this time. We will revisit this issue in a couple of months time.

    Thanks,

    Aneita

Comments (62)

  1. Brian Nguyen

    Hi Ben,

    This is something that is available for Stash but not Bitbucket at this time. I have put this issue on our backlog and we will look into it.

    Cheers, Brian

  2. Carl Gieringer

    It's confusing that Bitbucket doesn't allow this while Stash does. It took me a lot of googling to discover this page explaining that it is not possible to have branch prefixes when using JIRA and Bitbucket together. +1.

  3. Adam Cuzzort

    This is another confusing thing with the feature parity (or lack thereof) between Stash and Bitbucket. +1 for adding prefixes to JIRA -> Bitbucket agile integration. Gitflow requires those feature/ prefixes on branches to function and having to manually type it every time a branch is created creates plenty of opportunity for forgetting and messing up gitflow.

  4. Anonymous

    Was confused because I was seeing this in the documentation but couldn't use it with bitbucket. We really want this feature

  5. Andy Waschick

    Hear, hear. Let's keep this experience as consistent as possible. More than once I've created a branch in the wrong place because I was in a hurry. Aren't these tools supposed to make it easier to avoid dumb mistakes?

  6. Steffen Döll

    Vielen Dank für Ihre Nachricht!

    Sie erreichen mich heute nicht wie gewohnt in der Agentur. Ab dem 16.03.2015 bin ich gerne wieder persönlich für Sie da. Bitte beachten Sie, dass Ihre Nachricht nicht weitergeleitet wird.

    Ihr Anliegen lässt sich nicht so lange aufschieben? Kein Problem. Mein Kollege Martin Politzer (m.politzer@kuehlhaus.com, 0621 - 496083-45) hilft Ihnen gerne weiter.

    Viele Grüße Steffen Döll

  7. Daniel Sheard

    All I need to do is prefix branches with feature/ and it works as required but we're manually having to do this for each branch. Why can there not be a simple prefix field for Jira integration... this has been sat on for 2 years!

  8. Ben Tatham reporter

    @Brian Nguyen Any update on this? A while back someone at Atlassian said they were working on feature parity between Bitbucket Server (formerly Stash) and Cloud, but it seems this seemingly simple feature has been lost along the way. Given the prevalence of GitFlow (and other branching schemes) in the Atlassian tool suite, blogs, and the git world at large, I'm surprised this hasn't gotten more attention.

  9. Mike Conwell

    +1 Add to this the renaming of Stash to Bitbucket Server, and you can chase your tail for hours only to find out it's available on server but not cloud.

    We'll be having remote staff manually add the phrase "feature/" going forward, but quite the headache and prone to mistakes.

  10. Matteo Mosca

    I'd like to see this implemented as well. It is getting more and more complex to properly handle GitFlow within Jira integrated with Bitbucket. Convention based only branch linking is too restrictive.

  11. Mike Conwell

    Note: Doesn't even have to be a site settings thang. Could just be browser local storage memorizing the last branch name if used. feature/ begets feature/ bugfix/ begets /bugfix etc

  12. Brendan Lawlor

    Note that the new Pipelines feature allows us to distinguish branches based on prefix (feature/*) but the jira/bitbucket integration doesn't make it easy to insert this feature. Seems like a small change for a big win in terms of development ease.

  13. Aneita Yang staff

    Hi everyone,

    Thanks for your feedback on this ticket. Issue #12833 is another open ticket that is tracking this request. As that ticket has more votes and comments, I will update #12833 to include the main use cases that are mentioned on this ticket and mark this ticket as a duplicate.

    I encourage you to vote for and watch issue #12833 if it is something that you're interested in seeing as we regularly review the top voted issues for Bitbucket and provide updates on the ticket. Please feel free to also comment on that issue with any use cases that are not already covered.

    As mentioned on #12833, this request is not something that we will be addressing anytime soon as we're working on higher priority projects at this time. We will revisit this issue in a couple of months time.

    Thanks,

    Aneita

  14. Log in to comment