[Bamboo Knowledge Base]
Integrating Bamboo with Atlassian's JIRA applications 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 applications to work together simply requires you to set up an application link (two-way) between a JIRA application and Bamboo.
Note that application links have nothing to do with using a JIRA application as a user directory for Bamboo; these 2 configurations can exist separately. See also Linking to another application.
See Viewing Bamboo activity in a JIRA application for a full description of the benefits of integrating with Bamboo.
Briefly, these are:
|Release Hub||Check development activity and warnings by release version.||6.4+||5.4+|
|Development panel||See Bamboo development activity in JIRA applications.||6.2 +||5.4 +|
|Build result dialog||View detailed Bamboo build result information in JIRA applications.||6.2 +||5.4 +|
|Deployment dialog||View detailed Bamboo deployment information in JIRA applications.||6.2 +||5.4 +|
|Run Bamboo builds||Run a Bamboo build when releasing a JIRA application version.||4.4 +||3.0 +|
|Linked plan branches||Have Bamboo automatically link a plan branch with an issue.||4.4 +||3.0 +|
|Issues view||View issues linked to a build result.||4.4 +||3.0 +|
|JIRA application Projects||View the Bamboo builds that relate to a project or version.||4.4 +||3.0 +|
If you are using an earlier version of Bamboo and/or JIRA,applications 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 applications requires an application link between them. The application link needs both 2-legged (2LO) and 3-legged OAuth (3LO) authentication:
When you create a new application link between a JIRA application and Bamboo, both 2-legged (2LO) and 3-legged OAuth (3LO) are enabled by default.
An existing application link may need to have 2LO authentication explicitly enabled.
An existing application link between a JIRA application 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 a JIRA application as follows:
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 a JIRA application.
Having trouble integrating your Atlassian products with application links?
We've developed a guide to troubleshooting application links, to help you out. Take a look at it if you need a hand getting around any errors or roadblocks with setting up application links.