[Other doc versions]
See JIRA integration for a description of all the integrations you get when Stash is linked with JIRA.
You can also use JIRA for delegated user management. See External user directories.
This page describes how to link Stash to JIRA.
You can integrate Stash with one or more instances of JIRA by means of 'application links'. You set up application links either:
To link Stash to a JIRA server:
When you create a new application link between JIRA and an instance of Stash, 2-legged (2LO) and 3-legged OAuth (3LO) are enabled by default. 2LO is required for information from Stash to be included in the summaries in the Development panel of the JIRA issue; 3LO checks that a JIRA user has authenticated with Stash before they get to see the information in any of the details dialogs.
An older application link between JIRA and Stash will need to have 2LO authentication explicitly enabled.
An existing application link between JIRA and Stash (that perhaps used Trusted Apps authentication) needs to have 2-legged authentication (2LO) enabled for both outgoing and incoming authentication, so that information from Stash can be included in the JIRA 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:
The application link update process will involve logging you into Stash for a short time to configure that end of the link, before returning you to JIRA.
The following system plugins must be enabled in Stash. These are bundled and enabled by default in Stash 2.10 (and later):
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 (for example, for branches, commits and pull requests). That is, the details dialogs respect the access permissions that users have in the connected applications.
When Stash 2.10 or later is linked with JIRA 6.2 or later, you won't see the Source tab at the bottom of the JIRA View Issue screen any more.
Application links must have Trusted Applications and Basic Access authentication disabled. The Development panel in the JIRA issue view only supports OAuth authentication.
More detailed information about application links can be found on Configuring Application Links.
In addition, there are port restrictions, and other limitations, when linking Stash with JIRA Cloud. Pleases see Integrating JIRA Cloud with Bitbucket Server.
We have tried to make the integration of JIRA with Stash as straightforward as possible. However, we are aware of the following issue:
We apologise for the inconvenience. Please watch the issue to keep track of our progress.
There are a few scenarios where the integration of Stash with JIRA can produce an error or may not function as intended:
Unable to see the Development panel within a JIRA issue
You must have the 'View Development Tools' permission in order to see the Development panel. See the section (JIRA) Managing Global Permissions > Granting global permissionsfor details.
This can result if authentication for the application link has not been set up. See Troubleshooting JIRA Integration.
If you don't have permission to access the JIRA project then Stash is unable to display issues.
Stash can integrate with JIRA 4.3.x, or later. Some features require higher versions of JIRA to function properly. See Integrating Stash with Atlassian applications for details.
Stash doesn't check for invalid issue keys, such as UTF-8. An error will result if Stash tries to connect to an issue that doesn't exist.
Stash assumes that JIRA issue keys are of the default format (that is, two or more uppercase letters (
[A-Z][A-Z]+), followed by a hyphen and the issue number, for example STASH-123). By default, Stash will not recognise custom JIRA issue key formats. See Using custom JIRA issue keys with Stash for details.
Stash allows a user with global permissions of "Administrator" to create an OAuth only application link. You need to log in with a user having "System Administrator" privileges to create an application link using Trusted Applications.