Smart commits performed from Github are not updating Jira cloud issues as expected
Platform Notice: Cloud - This article applies to Atlassian products on the cloud platform.
Summary
Upon integrating Jira cloud with Github via the "Github for Jira cloud" addon (Available in the Atlassian marketplace: GitHub for Jira), the development information such as commits, pull requests, etc are syncing as expected in Jira issues, however, smart commits pushed via the commit messages are not updating Jira cloud issues as expected.
Environment
- You are using Jira cloud
- You have integrated Github cloud using the GitHub for Jira cloud addon
Diagnosis
- The integration addon configuration page in Jira cloud shows that the GitHub Organisation is connected.
- Development information such as commits, Pull requests, etc are synced as expected from Github to Jira issues.
- Smart commit syntax used in the GitHub commit message is correct: Process issues with smart commits
Possible Cause
- You are logged in with another email address that is not used in Jira and hence the smart commit information sent as the logged-in user does not have sufficient permissions to modify the issue in Jira.
- If you are using the same email address in both tools, the email address visible in GitHub has Private visibility.
Solution
As mentioned in our documentation here: Enable Smart Commits, if you're using Bitbucket Cloud or GitHub, all new repositories added to your linked Bitbucket Cloud or GitHub account have Smart Commits enabled by default.
In order to successfully modify the Jira issues through smart commits via Github, please ensure:
a) The email address used to login to the GitHub account is allowed to perform the actions in Jira (such as Transition issues permission, Ability to comment on issues, etc)
b) Set the email address visibility to Public by unchecking the settings "Keep my email addresses private": https://github.com/settings/emails