Stash is now known as Bitbucket Server.
See the

Unknown macro: {spacejump}

of this page, or visit the Bitbucket Server documentation home page.

When Stash is integrated with Atlassian JIRA, you can:

  • see, in Stash, the JIRA issues related to particular commits, as shown in the screenshot below.
  • see the JIRA issues related to particular pull requests.
  • click through to the issues in JIRA.
  • use JIRA for delegated user management. See External user directories.

The Commits tab for a repository in a Stash project, showing JIRA issues

Stash integrates with JIRA by means of an 'application link'. You can set up application links either:

  • during the Stash install process, using the Setup Wizard, or 
  • at any time after installation, as described below.

(warning)   Stash integration with JIRA may require an upgraded version of the FishEye/Stash plugin in JIRA. See JIRA compatibility for details about upgrading the JIRA FishEye/Stash plugin, and for download links to the upgraded plugin versions.

On this page:

Linking Stash with JIRA

To link Stash to a JIRA server:

Click Application Links (under 'Settings') in the Stash admin area.

Click Add Application Link:

Complete the application link wizard to connect Stash to your JIRA server. It is recommended that you make use of the automatic link-back from JIRA to Stash (you'll need JIRA system administrator global permission for that).

More detailed information about application links can be found on Configuring Application Links.

You're finished! No other configuration is required. Your JIRA issues will appear in the changesets and commit lists in Stash. On the JIRA side, the commits associated with a specific issue will now appear in the issue's Source tab.

Known issues with the JIRA integration

We have tried to make the integration of JIRA with Stash as straightforward as possible. However, we are aware of the following issues:

  • Stash only supports one JIRA server; we only pick the primary one.
  • There is no checking for project or issue-key validity; Stash may link to issues that do not actually exist.
  • Issue keys mentioned in commit messages for commits only appearing on a fork will not be indexed.

We apologise for the inconvenience. You can watch the issues below to keep track of our progress:

Troubleshooting integration with JIRA

There are a few scenarios where the integration of Stash with JIRA can produce an error:

The application link is misconfigured

This can result if authentication for the application link has not been set up.

You don't have permission to access the JIRA project

If you don't have permission to access the JIRA project then Stash is unable to display issues.

The JIRA server is of an unsupported version

Stash can integrate with JIRA 4.3.x, or later. Some features require higher versions of JIRA to function properly. See JIRA compatibility for details.

The JIRA issue key is invalid

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.

The JIRA issue keys are of a custom format

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.

The Application Link is created with OAuth only without the option to create a link using Trusted Applications

Stash allows a user with global permissions of "Administrator" to create an OAuth only application link. Log in with a user having "System Administrator" privileges to create an application link using Trusted Applications.

  • No labels