change default branch name in jira

We have integrated JIRA ondemand with bitbucket and love the fact that you can create a new feature branch from an issue. What we'd like is to change the default value of the branch name field to something lite "feature/<issue-key><issuename>".

Couldn't find an option to do that. Is it possible?



12 answers

1 accepted

Hi there, this is an error on our part.

The branch types attribute is only available for Stash when using the new Create Branch feature that is supported by Bitbucket. Inside of JIRA we currently have a general 'What's new' page that is the same for behind the firewall and OnDemand.

I'll check with our JIRA team to see if we can get this fixed, sorry for any confusion this has caused.

Cheers, Justen -- Bitbucket product manager

Is there an update for this? Been almost a year now. If this has been done can you point me to where the documentation is as I can't seem to get this working.

Now 2 years! This is a basic change and very critical to improving the efficiency of the tools

I'd love to have some flexibility regarding the branch names in Bitbucket. Any updates?

An implementation would be a nice way to celebrate the 4th anniversary of this feature request :)

Or maybe the fifth then :D

Please, implement configurable branch name prefix! Such a simple feature would bring a good value for our team.

To follow up on my own question. In the "What's new in JIRA 6.1" dialog that pops up when you enter ondemand there seems to have been added an option "branch type" which would solve my problem. But we don't get that option in our system. Is this not rolled out yet or do we have to configure it?

We'd love to see this as well. Our default branch naming scheme includes the year and month the branch was cut.

+1 for this. We like to have the user's name in the branch:


It would be nice if you Let the user build their branch names with the following variables:

  • Issue Type (bug/feature/etc)
  • Epic Name
  • Username
  • Issue Number
  • Issue Description

Thus currently the setting would be ${Issue Number}-${Issue Description}, and I would be able to accomplish what I want with ${Username}/${Issue Number}-${Issue Description}.

I think that would solve it for pretty much everyone here.



Hopefully this will be of use to some people. I am a fan of Tampermonkey scripts to tamper with websites to do what I want. In a need for this feature I have implemented this short script:


// ==UserScript==
// @name         Bitbucket: Better branch name
// @namespace
// @version      1.0
// @author       You
// @match*
// @grant        none
// ==/UserScript==
(function() {
    'use strict';
    var issueType = (window.location.href.match(/&amp;issueType=([^&amp;]+)&amp;/) || [])[1];
    var prefix = '';
        case 'Bug': prefix = 'fix/'; break;
        default: prefix = 'feature/'; break;
    $('#id_branch_name').val(prefix + $('#id_branch_name').val()).trigger('change');


It pulls the issueType from the href and prepends the appropriate prefix to the branch name. Feel free to tweak for our own prefixing needs.


Hey Jason,

This is in fact extremely useful! Thank you!

Awesome, thanks!

Today, this stopped working for me. Seems that Bitbucket removed the id from the form field and accessing it via name also doesn't seem to work. :(

We are also looking for this functionality with download JIRA (6.2) and Bitbucket. The branch type should be based on the issue type, so if I create a branch from a new feature or enhancement issue, the branch name would be e.g. feature/ABC-123, but if I create from a bug issue, then the branch name would be e.g. bugfix/ABC-456.

I +1 for this to be supported in Bitbucket too. We use git-flow and the missing branch type with Jira and Bitbucket is stopping us from using in-Jira branching.

+1 for us too

By the way, everyone should check out the feature request here: and upvote

@Fraser Hardy A workaround for using the git/hg-flow extensions is to prefix the auto generated branch name with feature/ and your flow commands should work as expected. Cheers!

How can I do that? Can´t find any documentation.

any update?

+1 for configurable branch name prefix feature implementation

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Wednesday in Jira

Make your Atlassian Cloud products more secure: our NEW admin security guide

Hey admins! I’m Dave, Principal Product Manager here at Atlassian working on our cloud platform and security products. Cloud security is a moving target. As you adopt more products, employees consta...

43 views 0 2
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you