Automatic branch detection does not create link to JIRA Automatically Edited


I created a build plan and configured and enable automatic branch detection and automatic creation for remote links for JIRA issues to plan branch as following screen shot.

Screen Shot 2017-09-26 at 9.32.40 AM.png


So I created Jira issue and then create branch by clicking "create branch " button on the right side menu.

Screen Shot 2017-09-26 at 9.41.00 AM.png


Then it redirect to branch creation bitbucket page and I created branch with the name which contains Jira issue key. 

After few moment, Bamboo successfully create plan branch and run build plan for newly created branch as I expected. 


However, it does not automatically create remote link from Jira issue to plan branches but only create a link in bamboo with manual creation button as following screen shot.


Screen Shot 2017-09-26 at 9.32.21 AM.png


So I searched if other people has similar issue and find out it was bug on previous version of bamboo and reported as resolved.


But I'm currently having similar issue and not sure how to resolve that.


Below is the current version information for applications we are using.

Bamboo: 6.1.1

JIRA: 7.3.6

Bitbucket: Cloud


Please let me know if there is a way to resolve it.


Thank you









1 answer

0 votes

What's the version of Jira, Bamboo and Bitbucket Server do you use?

we are using

Bamboo: 6.1.1

Jira: 7.3.6

Bitbucket: Cloud 


Can you please enable DEBUG logs for com.atlassian.bamboo.jira.issuelink.JiraBranchLinkingServiceImpl. 

You can do it in Administration > Log settings

Capture 2017-09-03 at 0.51.46.pngThen check messages in logs from JiraBranchLinkingServiceImpl

Here is the logs for JiraBranchLinkingServiceImpl

The last log says Authentication is required, but I already linked bamboo with Jira via OAuth for both incoming and outgoing connections.

2017-09-27 13:10:05,576 DEBUG [11-BranchJiraLinkingBackgroundThread:pool-18-thread-63] [JiraBranchLinkingServiceImpl] Detecting linked JIRA issues for branch 'BAM-PRTP13'

2017-09-27 13:10:05,587 DEBUG [11-BranchJiraLinkingBackgroundThread:pool-18-thread-63] [JiraBranchLinkingServiceImpl] Checking branch name 'CI-29-bamboo-test-issue-3' for issue keys

2017-09-27 13:10:05,589 DEBUG [11-BranchJiraLinkingBackgroundThread:pool-18-thread-63] [JiraBranchLinkingServiceImpl] Found issue key 'CI-29'

2017-09-27 13:10:05,589 DEBUG [11-BranchJiraLinkingBackgroundThread:pool-18-thread-63] [JiraBranchLinkingServiceImpl] Creating remote link from issue 'CI-29' to branch 'BambooTest - pull request test plan - CI-29-bamboo-test-issue-3'

2017-09-27 13:10:05,599 WARN [11-BranchJiraLinkingBackgroundThread:pool-18-thread-63] [JiraBranchLinkingServiceImpl] Could not link branch 'CI-29' to branch 'BambooTest - pull request test plan - CI-29-bamboo-test-issue-3'. Authentication required.


Also when I first attempt to automatic branch creation and check to see if it is creating Jira issue link correctly,  Bamboo asked for authentication from Jira side with currently logon Jira user.


Screen Shot 2017-09-27 at 9.27.46 AM.png


So authenticate and allow read and write access as Jira admin user for Bamboo application.

 Screen Shot 2017-09-27 at 9.34.28 AM.jpg


I'm not sure if there is anything that i missed?







@Alexey Chystoprudov Please see my reply above. I still could not figure out how to fix that......

@brent bae, sorry for delay. Looks like it requires more investigation. Can you please raise an issue at Our support engineers will do their best to solve this issue

I have this exact same problem.  We are using Jira Cloud connected to internal Bamboo and Bitbucket Servers.  All other application-link related functionality works.

 Jira 4212ad73
Bamboo version 6.2.1 build 60208 - 27 Sep 1

Bitbucket 5.4.0


I found the Jira issue for this.  It appears to be Resovled.  However, I can confirm this problem still exists.

Suggest an answer

Log in or Join to answer
Community showcase
Renan Battaglin
Published May 18, 2017 in Bamboo

FAQ: How to Upgrade Bamboo Server

Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...

1,061 views 0 5
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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot