[Other doc versions]
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.
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.
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:
In JIRA, you can see details for a commit made in Stash. And you can click through to go straight to the commit in Stash: