Forums

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

branching model mapping broken?

Alexander Noteboom
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!
August 6, 2019

I was so happy when we were able to configure a branching model, at the end of last year.  

When creating a branch from a Jira issue it would now automatically add feature/  to the branch name.  

There was one thing:  we also wanted to have IssueType 'Bug' to have feature/ in the branch name. So Atlassian came to the rescue.  When you disable Bugfix type in the branching model, it would automatically use feature/.  Awesome.

But now this last thing seems to be broken again.  When I create a branch from a Jira Bug,  it doesn't add feature/ anymore. 

I've checked all the settings, but it seems to be ok. We did add some branch permissions a while ago, but I don't think that should interfere.

Does anyone else have this problem?

 

(We are using Bitbucket Cloud)

1 answer

1 accepted

1 vote
Answer accepted
Nithin Peter
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
August 6, 2019

Thanks for reporting the issue. This should be fixed by now. Jira issue type 'Bug' now correctly maps to 'feature/'.

Sorry for the inconvenience caused.

Alexander Noteboom
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!
August 7, 2019

Nithin,

Thanks. It works again.  Really appreciate it.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events