Enabling DVCS Smart Commits
When you manage your project's repositories in Bitbucket or GitHub, or use FishEye to browse and search your repositories, you can process your JIRA Software issues using special commands in your commit messages.
- comment on issues
- record time tracking information against issues
- transition issues to any status (for example 'Resolved') defined in the JIRA Software project's workflow.
Learn more about using Smart Commits: Processing issues with Smart Commits.There are other commands available if you use Crucible for code reviews. See Using Smart Commits in the FishEye/Crucible documentation.
Get Smart Commits working
There are a couple of things you need to set up to get Smart Commits working.
First, link JIRA Software to the other application
Smart Commits relies on either the JIRA DVCS Connector Plugin or an application link:
|JIRA DVCS Connector||
The JIRA DVCS Connector Plugin is bundled with JIRA Software , but if necessary, a JIRA administrator can install it directly from within the JIRA administration area. See Installing add-ons for more information.
A JIRA administrator with access to the Bitbucket Cloud or GitHub account must set up OAuth authentication with JIRA Software .
|Application link||See Linking a Bitbucket or GitHub repository with JIRA.|
Then enable Smart Commits in JIRA Software
Smart Commits must be enabled in JIRA Software :
All new repositories added to your linked Bitbucket Cloud or GitHub account have Smart Commits enabled by default. However, a JIRA administrator can disable that if necessary, and can also enable or disable Smart Commits for individual repositories.
Control whether Smart Commits are enabled for new repositories:
Enable or disable Smart Commits on individual repositories:
A JIRA administrator can control Smart Commits for each account in the connected application (Bitbucket Server, FishEye or Crucible).
Enable or disable Smart Commits on individual accounts:
Note that elevated access rights in JIRA applications can result from the way that Git (and Mercurial) allow commits to be attributed to a user other than the user pushing a change to the repository.
If this seems like a risk for your situation, then you should consider disabling Smart Commits in your JIRA application instance.
Forks and Smart Commits
If you use forks in your workflow, the DVCS Connector records each repository that contains a Smart Commit message. It actually processes the Smart Commit message only the first time it encounters it. When you view the commit tab in JIRA Software , you can see which forks include that particular commit:
Was this helpful?
Thanks for your feedback!