Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

New Bitbucket Cloud branching model is a little restrictive

Matteo Melli
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
October 12, 2018

I started using Branching model in Bitbucket Cloud. I feel like the settings are a little restrictive.

Instead of providing 4 fixed types of issue, why don't let the user to specify the issueType by himself (as strings). Is there an implicit meaning behind any of those 4 types?

I'm thinking about Jira integration.

First question. We have created a issueType named "Release" that we use to track the releases workflow. How can I automate the selection of the Release Type (which sets the "release/" prefix) when I click "Create Branch" on Jira Issue Page?

How I can change the default base branch from master to develop?

Moreover, using Git-Flow, we have only a single prefix for bugfixes and features, which is "feature/". This is because Git-Flow implementation doesn't make difference between them, since they have the same workfow (I'm not talking about hotfixes which are different).
Now I can't even automate this behaviour, because when I create a branch from a Bug in Jira, Bitbucket suggests the Type for Bugfix issues, which can't have the same prefix as the Feature one (the settings page doesn't allow me to save the same prefix for different types).
The only chance is to disable Bugfix branch prefix and manually select the correct Type (and prefix) from the "Create Branch" form.

My idea to improve the behaviour is the following:

  • Specify different issue types by custom names, allowing the user to add and remove types based on his needs (the starting set could be the current one);
  • For each type, the user has to specify the Name (for human readability), the issueType (or even multiple issueTypes for easier configuration), the prefix (opional) and the base branch.
    • Example - Name: "Feature or Bugfix", issueType: ["Story", "Bug"], prefix: "feature/", Base Branch: "develop"
    • Another example - Name: "Release", issueType: "Release", prefix: "release/", Base Branch: "develop"
    • Another example - Name: "Hotfix", issueType: "Hotfix", prefix: "hotfix/", Base Branch: "master"
  • When the "Create Branch" forms opens, check the issueType value in querystring and pre-fill the Type select menu. This selection has to trigger the right selection of the "From branch" menu (using the specified base branch) and the prefix of the branch name.

This way the integration with Jira will be very flexible and convenient.

 

What do you think?

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events