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
<command> <issue id>
You can link to a single issue or multiple issues. The
<issue id> can take any 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 work to close an issue.
|resolve an issue|
fix bug #89
fixes issue #746
|reopen an issue|
|mark an issue on hold|
|mark an issue wontfix|
|mark an issue invalid|
|link to a changeset for the issue|
re bug #55
see #34 and #456