Enabling DVCS Smart Commits
Get Smart Commits working
Smart Commits relies on the JIRA DVCS Connector Plugin when your repositories are hosted in Bitbucket Cloud or GitHub. The plugin is bundled with JIRA Software , but if necessary, a JIRA administrator can install it directly from within the JIRA administration area. See Installing Marketplace apps for more information.
There are, however, a couple of things that need to be set up to get Smart Commits working:
Link JIRA Software with the DVCS account
A JIRA administrator with access to the DVCS account must set up OAuth authentication between JIRA Software and the Bitbucket or GitHub account. See Linking Bitbucket Cloud and GitHub accounts to JIRA Software for details.
For FishEye/Crucible, there just needs to be an application link set up between JIRA Software and FishEye/Crucible.
Enable Smart Commits in JIRA Software
All new repositories added to your linked DVCS account have Smart Commits enabled by default. However, an 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:
- Log in to JIRA Software as a user with administrative permissions.
- Go to Administration > Applications > DVCS accounts.
- Click the
(settings) icon for the account. - Click Enable Smart Commits on new repositories.
Enable or disable Smart Commits on individual repositories:
- Log in to JIRA Software as a user with administrative permissions.
- Go to Administration > Applications > DVCS accounts.
- Check (or clear) the Smart Commits option for a repository.
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:
