Stash is now known as Bitbucket Server.
See the

Unknown macro: {spacejump}

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

Skip to end of metadata
Go to start of metadata

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.


Transition JIRA issues automatically

STASH 3.2+ JIRA 6.3.3+

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, but a Stash administrator can disable publishing for a particular repository on the JIRA triggers tab of the repository's settings. You may need to do this if duplicate repository events are causing incorrect issue transitions. Note, JIRA automatically removes duplicate commit events (JIRA 6.3.3+) and duplicate branch creation events (JIRA 6.3.11+).


See all related branches, commits and pull requests in a JIRA issue

STASH 2.10+ JIRA 6.2+

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.

 

Create Git branches from within JIRA and JIRA Agile

STASH 2.8+ JIRA 6.1+

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.

 

Transition JIRA issues from within Stash

 STASH 2.8+ JIRA 5.0+

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.

 

See issues from multiple instances of JIRA

STASH 2.7+

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.

 

Use JIRA issue keys in markdown

STASH 2.7+

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.

 

See the details for JIRA issues

STASH 2.1+ JIRA 5.0+

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:

 

See the JIRA issues related to commits and pull requests

STASH 2.1+ JIRA 5.0+

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.

  • No labels