Hello, is it possible to disable the Smart Commits feature in Jira Cloud?
Hi Nik, it depends on how GitHub is connected.
If your repos are listed under Settings > Jira apps > DVCS accounts (the older connection), you can turn Smart Commits off there: under ••• > Default repository settings for new repos, or with the checkbox on each repo row.
New GitHub connections no longer go through that page. On a current Cloud site, DVCS accounts only offers Bitbucket Cloud, and the GitHub link sends you to the GitHub for Atlassian app (screenshot). As far as I know, that app has no Smart Commits switch. Smart Commits only run when the commit email matches a Jira user who has Transition, Comment or Log work permission, so permissions are the only lever there.
Which connection are you using?
Thanks for the swift response!
It's a new GitHub connection, so doesn't appear in DVCS I guess
Smart Commits only run when the commit email matches a Jira user who has Transition, Comment or Log work permission, so permissions are the only lever there.
You mean disabling specific users' ability to comment on Jira tickets in general? Or is there a separate user permission for 'Allowed to comment/add time tracking via Smart Commits'?
Hi Nik, there's no separate Smart Commits permission, so it's the first one.
Like Pavel said, a smart commit runs as the Jira user whose email matches the commit author. Jira then checks that user's normal permissions in the space. #comment needs Add comments, #time needs Work on work items and #transition needs Transition work items.
So you'd remove it for that user in that space in general, via the permission scheme. I haven't found a way to block only the commit route.
For #time there's a blunter switch. It only works when time tracking is on for the site, so turning time tracking off stops it too, for everyone.
The requirements per command are here: https://support.atlassian.com/jira-software-cloud/docs/process-issues-with-smart-commits/
No, there’s no separate permission for Smart Commits. They run as the Jira user whose email matches the commit email and use that user’s normal permissions (comment, log work, transition). Taking those away would also block them in Jira itself, so I wouldn’t go that way.
Two options that only affect Smart Commits:
Hi @Tsonchev, Nik
Yes! It is possible to disable Smart Commits in Jira Cloud, provided you have the necessary administrative permissions.
You can manage this through the repository integration settings:
You may also be able to disable Smart Commits by default for new repositories using the Enable Smart Commits for all repositories setting, if available.
Hi Nik, adding sources to the two options above, since a few details matter.
The DVCS accounts steps only apply to the old connector. Atlassian's FAQ says DVCS users "should migrate to the GitHub for Atlassian integration", and for that app I couldn't find a Smart Commits toggle, only prerequisites: GitHub and Jira emails must match, and "Keep my email addresses private" must be unchecked.
https://support.atlassian.com/jira-cloud-administration/docs/github-integration-faq/
Option 1, noreply email. With email privacy on, web commits get a no-reply author address. For command-line commits, each developer sets git config user.email to their GitHub noreply address. Per user, not enforced.
https://docs.github.com/en/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address
Option 2, ruleset (Enterprise plan). Add "Restrict commit metadata", set the commit message to "Must not match a given regex pattern", with something like #comment|#time plus your workflow's transition names (the command is #<transition_name>). Caveats from GitHub's docs: it only blocks updates to the branches the ruleset targets, and GitHub recommends a limited set such as main; with squash merges, only the resulting commit is checked; and it's "not intended to replace security measures". Run it in "Evaluate" mode first.
https://docs.github.com/en/enterprise-cloud%40latest/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/available-rules-for-rulesets
https://docs.github.com/en/enterprise-cloud%40latest/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/creating-rulesets-for-a-repository
Command syntax: https://support.atlassian.com/jira-software-cloud/docs/process-issues-with-smart-commits/
(Disclosure: I work on Linkwright, another GitHub connector for Jira.)
It looks like you're new here. Sign in or register to get started.