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.
See Viewing Bamboo activity in JIRA for a full description of the benefits of integrating JIRA with Bamboo.
Briefly, these are:
|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||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.
|Earlier versions of JIRA do not support the Development panel feature.|
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.
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:
- Go to the JIRA admin area and click Add-ons > Application Links.
- Click Edit for the app link with the other application.
- For both Outgoing Authentication and Incoming Authentication:
- Click OAuth
- Check Allow 2-legged OAuth.
- 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.
- 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.
- 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 (see BAM-3492).