Integrating Bamboo with JIRA

Integrating Bamboo with Atlassian's JIRA combines Bamboo's continuous integration capabilities with your issue tracker to give you a unified view of your software development project.

Configuring Bamboo and JIRA to work together simply requires you to set up an application link (two-way) between JIRA and Bamboo.

Note that application links have nothing to do with using JIRA as a user directory for Bamboo; these 2 configurations can exist separately. See also Linking to another application.

On this page:


See Viewing Bamboo activity in JIRA for a full description of the benefits of integrating JIRA with Bamboo.

Briefly, these are:

Integration feature Description


JIRA Bamboo
Development panel See Bamboo development activity in JIRA 6.2 + 5.4 +
Build result dialog View detailed Bamboo build result information in JIRA 6.2 + 5.4 +
Deployment dialog View detailed Bamboo deployment information in JIRA 6.2 + 5.4 +
Run Bamboo builds

Run a Bamboo build when releasing a JIRA version

4.4 + 3.0 +
Linked plan branches

Have Bamboo automatically link a plan branch with a JIRA issue

4.4 + 3.0 +
JIRA issues view

View the JIRA issues linked to a build result

4.4 + 3.0 +
JIRA Projects

View the Bamboo builds that relate to a JIRA project or version

4.4 + 3.0 +

If you are using an earlier version of Bamboo and/or JIRA, you can also download an older version of the JIRA Bamboo plugin from the Atlassian Plugin Exchange. However, we strongly advise you to upgrade JIRA to version 6.2 or later and Bamboo to version 5.4 or later, to get the most out of Bamboo - JIRA integration.


Requirement Description

JIRA 6.2+

Earlier versions of JIRA do not support the Development panel feature.
Bamboo 5.4+  
JIRA/Bamboo Applink

See below for details about application links.


Users will require the 'View development tools' permission in JIRA.

Issue key The issue key must be included in the commit message, and must use the default JIRA issue key format.


Integration of Bamboo and JIRA requires an application link between them. The application link needs both 2-legged (2LO) and 3-legged OAuth (3LO) authentication:

  • 2LO is required for information from Bamboo to be included in the summaries in the Development panel.
  • 3LO checks that a user has authenticated with Bamboo before they get to see the information in any of the details dialogs. Users who can see summarized data in the Development panel may not have permission to see all the information that contributed to those summaries and which is visible in the details dialogs. That is, the details dialogs respect the access permissions that users have in the connected Bamboo server.

When you create a new application link between JIRA and Bamboo, both 2-legged (2LO) and 3-legged OAuth (3LO) are enabled by default. 

  • You will need to set up a two-way link. That is, select the Create a link back to this server option when adding the application link.

An existing application link between JIRA and Bamboo may need to have 2LO authentication explicitly enabled.

  Click here to see how to enable 2-legged OAuth...

An existing application link between JIRA and Bamboo (that perhaps used Trusted Apps authentication) needs to have 2-legged authentication (2LO) enabled for both outgoing and incoming authentication, so that information from the application can be included in the Development panel summaries.

When updating an older application link to use OAuth, 3-legged authentication is applied by default, but you need to explicitly enable 2LO. Enable 2-legged authentication for the application link from within JIRA as follows:

  1. Go to the JIRA admin area and click Add-ons > Application Links
  2. Click Edit for the app link with the other application.
  3. For both Outgoing Authentication and Incoming Authentication:
    1. Click OAuth
    2. Check Allow 2-legged OAuth.
    3. Click Update.

The application link update process will involve logging you into the other application for a short time to configure that end of the link, before returning you to JIRA.

Note that:

  • Application links must have Trusted Applications and Basic Access authentication disabled. The Development panel in JIRA only supports OAuth authentication.
  • You will need to configure 2-legged OAuth enabled for both incoming and outgoing authentication in both JIRA and Bamboo for your application link. 
  • See Configuring Authentication for an Application Link for more information.
  • If you are running Bamboo behind a proxy, you may need to configure the AJP connector.


Known issues

  • JIRA and Bamboo cannot run in the same Tomcat instance due to a known issue with the Bamboo plugin for JIRA (see JRA-19662). 
  • If integrating Bamboo with JIRA,  you should not change the JIRA project key format from the default, as Bamboo only supports the default project key format.

If you need further help, please raise a support request in our support system, in the Bamboo project. You may also want to view articles in the Bamboo Knowledge Base and browse our forums.

Was this helpful?

Thanks for your feedback!

10 Archived comments

  1. User avatar

    David Corley

    In section 1, if no Jira project keys are specified, will all projects be associated with the Bamboo server, and if not, is there a way to associate all project without having to enter every project key?

    17 Jan 2011
  2. User avatar

    Dave Thomas

    The JIRA Bamboo plugin doesn't have information about compatibility with bamboo for any recent versions of the plugin. How can we tell if it's safe to upgrade?

    We're running Jira 4.3.3, which shipped with version 4.1.3 of the plugin. I'm not sure why the 4.2.x version of the plugin wasn't shipped with Jira .4.3.3, but we're interested in moving to applinks since we have multiple bamboo servers. Without bamboo compatibility information, however, it's hard to tell if this is an option or not.

    27 May 2011
  3. User avatar



    I'm having trouble with application link between JIRA and bamboo.

    I posted the question in the Answers below. But, I can not get any help.

    For your information, we're using JIRA 4.3 and Bamboo 3.2.

    Both configurations are OK.

    Because configurations  are showed in administration section of two applications.

    How can I sovle it?

    What part of these applications  do I have to check??

    11 Oct 2011
  4. User avatar

    Tobias Kremer


    I am running Jira over HTTPS (see but now I have problems connecting Bamboo to Jira.

    I was getting SSLHandshakeExceptions as I used a certificate signed by our in house CA witch bamboo did not trust. After some tempering with wrapper.conf I managed to set the Truststore to use the certificate I use in Jira.

    Now I can connect to Jira again. But I can not connect to Atlassian Plugin Exchange to load Plugin-Updates.

    I guess the main problem is that I am just to stupid to create a workingtrust store.


    Would have been great if this page or the "Running Jira over SSL" page would contain istructions how to configure bamboo to talk to Jira using an encrypted connection.


    Tobias Kremer

    12 Oct 2011
    1. User avatar

      Daniel Herrera

      Hello Tobias,

      I am having the exact same problem.  I am trying to get my Bamboo version 4.4.5 build 3507 to connect to JIRA v4.4.1 that is HTTPS.

      Do you remember what you had to do to the wrapper.conf file?

      Have you come up with a better solution?

      Thanks in advance,

      Kurt Frank

      11 Jun 2013
  5. User avatar

    Aaron Carter


    So my organization is essentially using JIRA, BAMBOO, Crucible and Confluence, however our JIRA Administrator has constructed the integration between these products so that we can only open tickets under a single project.  Due to the fact that we work on many projects and have about 7 products that under ongoing development with the Agile methodology we would like to have the option to open up new projects in JIRA.  However our JIRA admin states that we can only have a single JIRA project in order to work with Bamboo and Crucible.  So my question is pretty simple can we have multiple projects setup in JIRA and links established for each project in Bamboo, Crucible and Fisheye?  Also is just have one project setup in JIRA to manage multiple projects and products the optimal way to go?

    10 Jul 2013
  6. User avatar


    Hi everyone,

    I set up the application links from JIRA to Bamboo and vice versa as trusted applications and they seem to be working. I can see all related issues in my Bamboo builds. However, opening the "Builds" tab on an issue in JIRA does show the login page for Bamboo. The Bamboo anchor points to our installation and works just fine, i.e. clicking it directs me to Bamboo and shows my projects (no login required, authentication for all my atlassian apps is done via crowd).

    Trying to authenticate via the login page in JIRA with my crowd credentials directs me to an url like https://myserver/jira/%2Fajax%2Fbuild%2FviewBuildResultsByJiraKey.action and leads to a document not found error.

    Thus, I am not able to authenticate from the JIRA "Builds" Tab to my Bamboo app and am therefore not able to see any build details in my JIRA issues.

    What could I be doing wrong in this setup?

    Thx for your help

    16 Aug 2013
  7. User avatar



    I'm experiencing the exact same situation as Lukas. 

    Not sure what could be done differently. I have opened a support ticket, so hopefully I'll get some good pointers from Atlassian

    28 Aug 2013
  8. User avatar



    The problem was that we have a apache httpd as proxy. 

    I recreated the application link (trusted application) using the local machine name instead of pointing to the apache proxy.

    29 Aug 2013
  9. User avatar

    aditya verma

    Who can Provide help if we need to disintegrate Bamboo JIRA and Confluence on different Servers.


    Right now all three are on one single server, need to separate them on different servers.

    10 Apr 2015
Powered by Confluence and Scroll Viewport