Resolve issues automatically when users push code

This page is about transitioning issues in the Bitbucket Cloud issue tracker. If you have Bitbucket Cloud integrated with Jira Software, then you can use Smart Commits instead.

Bitbucket Cloud can resolve Bitbucket Cloud tickets automatically when people push updates to your Bitbucket Cloud repository.  They can specify commands and issues in commit messages, like this:

hg commit -m "fixes #6, resolve ticket #5 and see ticket #9 and ticket #5 in the tracker"

On Bitbucket, the commit message appears with links to each issue:

When you transition an issue with a commit message, the system cross-references the commit from the issue:

Including Issues in a Commit Message

To link commit to an issue from a commit message, include an command-issue pair somewhere in your commit message. This pair takes the following format:
<command> <issue id>

You can link to a single issue or multiple issues.  The <issue id> can take an of the following forms:

#4711
issue #4711
bug #4711
ticket #4711

You should always include the # (pound sign or hash mark) if you want to ensure that links back to the issue resolve.  If you omit the # (pound sign or hash mark), links from a changeset do not resolve.

Each action supports multiple <command> keywords. The following table lists the actions you can perform through a commit and the acceptable commands for that action.  All the keywords are case insensitive. So, for example, both close and Close work to close an issue.

Action Command Keyword Examples
resolve an issue
  • close
  • closes
  • closed
  • closing
  • fix
  • fixed
  • fixes
  • fixing
  • resolve
  • resolves
  • resolved
  • resolving
close #845
fix bug #89
fixes issue #746
resolving #3117
reopen an issue
  • reopen
  • reopens
  • reopening
reopen #746
reopening #78
mark an issue on hold
  • hold
  • holds
  • holding
holds #123
mark an issue wontfix
  • wontfix
wontfix #12
mark an issue invalid
  • invalidate
  • invalidates
  • invalidated
  • invalidating
invalidates #45
link to a changeset for the issue
  • addresses
  • re
  • references
  • ref
  • refs
  • see
re bug #55
see #34 and #456

Last modified on Nov 8, 2017

Was this helpful?

Yes
No
Provide feedback about this article

Not finding the help you need?

Ask the community

Powered by Confluence and Scroll Viewport.