We recently upgraded from Stash 3.8 to Bitbucket Server 4.5.2. After doing so we noticed a quirk/issue with our JIRA to Bitbucket Server integration:

In our Bitbucket Server repository, we had enabled 3 of the 4 branch prefixes for our branching model:

1. Feature, set with branch prefix "issue/"
2. Hotfix, branch prefix "patch/"
3. Release, branch prefix "release/"

With Stash 3.8, if we used JIRA's Stash integration to create a branch from an issue of type "Bug" (which does not map to any of the 3 Bitbutcket Server branch types we have configured), Stash's "Create branch" screen would simply default to a Branch Type of "Feature" and give us the expected branch prefix "issue/".

Now, after we upgraded to Bitbucket Server, if we use the same JIRA integration with Bitbucket Server to create a branch from an issue of type "Bug" (which still does not map to any of the 3 Bitbutcket Server branch types we have configured), Bitbucket Server's "Create branch" screen would default to a Branch Type of "Feature", but it will NOT append the branch prefix "issue/" - it won't append anything in this case.

If the user toggles the Branch Type dropdown (i.e. even though it shows "Branch Type" set to Feature, click the "Branch Type" dropdown and select Feature again), then the expected branch prefix "issue/" will be appended.

We noticed the issue in Bitbucket Server 4.5.2 (because that's what we upgraded to from Stash 3.8), but after some testing trial and error I discovered this issue first cropped up in Bitbucket Server 4.1.6 (or at least, sometime after Bitbucket Server 4.0.1 - which still behaved like Stash 3.8.x, 3.9.x, etc.).

I've attached a couple of screenshots to illustrate this.

We would like the old behavior back (i.e. the pre-Bitbucket Server 4.1.6 behavior).

Or if we can't get the original behavior, if would could assign the same branch prefix to multiple branch types in Bitbucket Server - so if we could set "Feature" and "Bugfix" branch types to the same prefix ("issue/" in our case), that would also be acceptable.

Basically we don't need to differentiate between Features and Bugfix branches with different branch prefixes - we prefer them to be under the same prefix.