The "create branch" example contains a space, but git does not allow spaces

This question is in reference to Atlassian Documentation: Referencing issues in your development work

The "create branch" example in the "Referencing issues in your development work" section of the documentation contains a space, but git does not allow spaces in branch names!  I tried using an underscore in between the Issue ID and the other text, but JIRA didn't pick it up.  How do you get JIRA to pick up the issue number within the name of the branch with JIRA doesn't seem to pick the issue number up when the branch name is of the form "eng_AI-12345" or "eng-AI-12345-fix_widgets"?

2 answers

0 votes

Hi Thomas,

What development tool are you integrating with JIRA and what version of JIRA? If you can log a support ticket the support team can help investigate further.

The formats you have described should work, although you could try prefixing it with the issue key, i.e. AI-12345_description 

If you want the username first you can use 'username/AI-12345_description'

Another way to create the branch is from within JIRA itself which will automatically populate the issue key into the branch name.


We are using hosted JIRA v1000.482.3 at with GitHub.

Why is it necessary to use AI-12345_fixwidgets instead of eng_AI-12345_fixwidgets?  Your documentation does not indicate such a requirement:

Include the issue key in the branch name when you create the branch.

For example, if you name your branch "TIS-2_feature", the TIS-2 issue in JIRA will automatically transition from 'To Do' to 'In Progress'. (Note that Git doesn't allow spaces in branch names.)

Perhaps the documentation could be updated if this is, indeed, a requirement?

Also, since the Pull Request has already merged at this point, how can I provide a link to the GitHub issue (or branch, or commit) in a JIRA comment that will get picked up and shown in the Development section of the Issue?  I'm not seeing an explanation in the documentation of how I can provide a Pull Request number in an Issue comment that will be interpreted as such.

Thank you for your assistance.

Are you able to log a support ticket ( I've poked around and it should be working with eng_AI-123_fix as the branch name or PR name, support could take a deeper look then.

Unfortunately there is no support for linking in Github issues into the dev panel section of the issue. Once the PR is closed.

Is there no way to link to a Pull Request or a commit in a comment on an Issue, then?  That seems like at least as common of a use case as linking to the Issue in the git commit comment or the GitHub Pull Request.

The dev panel shows information based on the integrations, there is currently no support for manual association.

You might be able to rename the pull request to be picked up, but I'm not sure if you can rename merged PRs.

If you are looking to link a Github issue to the JIRA issue you could use the issue links to create a web link ( in the JIRA issue to your Github issue, these would show in the main issue view.


0 votes
Paul Watson Atlassian Team Nov 01, 2016

Thanks Thomas, I've updated the page (and a few related pages too).

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,815 views 18 22
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