JIRA integration

You can also use JIRA for delegated management of your Stash users. See External user directories.

Your Stash administrator needs to set up linking with JIRA before you'll see these work.

The Release Hub shows the progress of a version, so you can determine which issues are likely to ship at a glance. With JIRA and Stash connected, the commits related to each issue are shown, helping you to spot potential development issues that could cause problems for a release.

When you are ready, you can also release the version from the Release Hub, which marks the version as complete, moves incomplete issues to other versions, and triggers release builds (if JIRA is connected to Bamboo).

To view the Release Hub (with the project sidebar enabled), navigate to a project, click on Releases, then select a version listed. See Checking the progress of a version for more detailed information about using the Release Hub in JIRA.

Your JIRA workflow can now respond to events in your linked development tools. For example, when a pull request is created, your JIRA workflow can be configured to automatically transition the related issue. Configure this from transitions within the JIRA workflow editor – see Advanced workflow configuration in the JIRA documentation:

The events available in Stash are:

• Branch created
• Commit created
• Pull request created
• Pull request merged
• Pull request declined

Stash events are published by default. We recommend that you use the latest version of JIRA to ensure that duplicate events are handled correctly. JIRA automatically removes duplicate commit events in JIRA 6.3.3+ and duplicate branch creation events in JIRA 6.3.11+.

Get visibility into the Stash branches, commits and pull requests related to work on a JIRA issue, right in the context of the issue in JIRA (and JIRA Agile). 

Click the links in the Development panel to see details of the work that's been done. You can start creating a pull request from the Commits details dialog, or click through to see a changed file, or the full commit, in Stash.

You can start creating a branch from a JIRA issue. This gives you a faster workflow from picking an issue to starting coding.

Stash will suggest the branch type and branch name, based on the JIRA issue type and summary – you can change these, of course.

You can easily transition a JIRA issue from within Stash. For example, when creating a pull request you may want to transition the issue into review. Click on a linked JIRA issue anywhere in Stash to see a dialog with the available workflow steps:

Click on a step and complete the fields as required. If there are custom fields that are unsupported by Stash, just click Edit this field in JIRA to transition the issue directly in JIRA.

Stash can link to more than one JIRA server at a time, so different teams can work with their own projects in different JIRA instances, or a single team can link to issues across multiple JIRA servers. Read more about linking Stash with JIRA.

When you mention a JIRA issue key in Stash, for example in a pull request description or a comment, the key gets automatically linked:

Click on the linked key to see details for the issue.

Click a linked issue key anywhere in Stash to see the details of that issue in a dialog. And you can just click the issue key at the top of the dialog to go straight to the issue in JIRA:

Stash recognises JIRA issue keys in commit messages, and displays the keys as links on the Commits tabs for both the repository and pull requests:

Click on the linked key to see details for the issue.