How to create additional branch prefix

[Walter Davies]

I'd like to add at least one branch prefix to the existing list (e.g `feature/`, `bugfix/`, &c). Can this be done within Bitbucket or can I only push a new named branch and hope for the best? Because of our workflow (the workflow that seems to be encouraged by Atlassian, for that matter), it would be helpful if additional branch prefixes were available for creating new (sub)-branches from tickets. 

[Jurgen Hannaert]

It would be very useful to be able to create additional custom prefixes.

[Walter Davies]

It really looks like the only option is to rename one of the existing prefixes but that there is no ability to create additional prefixes. 

I'd really like to be wrong about this. In the meantime, I'll just push a long-running branch and hope for the best. 

And no, I do not find that to be satisfactory. I can understand having an upper limit on branch prefixes (after all, nobody should ever need more than 640k RAM), but supporting Branching Strategies really seems to imply being able to make further use of Branching Strategies. It would be yet another in a long line of disappointments if this is not the case. 

[Michael Rüegg _Mibex Software_]

Hi,

For Bitbucket Data Center, if you do not mind a commercial app, our Create Branch Wizard for Bitbucket allows you to do this.

Besides having flexible branch prefixes, you can also customize your branch names completely based on various fields of a Jira issue the branch is created from. Here's an example:

my-custom-branch-prefix/$fixVersion/$issueType/$issueKey-$issueSummary 

leads to e.g.

my-custom-branch-prefix/1.0.1/bug/PROJ-11-fix-iso-date 

Furthermore, the app makes sure that the right repository (the one from the Jira issue project) is selected in the create branch dialog, whereas Bitbucket shows the most recently selected repo.

If you are interested in a version for Bitbucket Cloud, please vote on this feature request.

Best regards,

Michael (app vendor)

[Walter Davies]

Thanks @Michael Rüegg _Mibex Software_, 

I'm not opposed to a commercial app, but I'm using Bitbucket Cloud and, truly with all due respect, have grown so weary of voting on feature requests for Bitbucket incompleteness that I really just can't be bothered anymore. The Mibex solution sounds really great but is massive overkill for our needs and if Atlassian can't be bothered to provide basic functionality in support of their workflow then… well, that's just what I've gotten used to. 

[Newthon Junior]

I completely agree with you @Walter Davies, if an application is not capable of providing basic functions without this voting scheme I am out. This clearly demonstrates monetary interest rather than honoring customers. You need to beg people to vote on requests that are hidden and when they exceed 100 (after a long 4 years, they take longer years to implement. When they do implement)