When a Git commit message contains a Jira ticket number, eg ELE-1234 then usually on committing the corresponding Hira ticket is updated with commit info. Sometimes this seems to fail commits where a valid ticket number has been correctly specified - no commit info ends up in a Jira ticket. What can I do to find out what's causing this/how to fix it? Looking at the OnDemand Bitbucket Importer plugin info on our Manage Add-Ons page doesn't help - there's no logging/configuration info there.
Thanks for the response. We hadd checked all of those to no avail. It turned out that the DVCS add-on (on /admin/ConfigureDvcsOrganizations!default.jspa) was showing that it hadn't synced for the project in question for several days. Choosing to 'Sync Repo' got commit messages appearing in tickets again. (I had been looking at the wrong add-on to begin with!).
In some cases, the user doesn't have permission to log work. You can check the permission scheme for the project where the tickets reside.
A few other possibilities:
•The email address cannot be found in JIRA.
•The are more users in JIRA with the same email address. As emails are used to map to JIRA users, they should be unique in JIRA to have the feature working.
•The email address is not configured in Git or Mercurial. User should configure an email address in .hgrc or .gitconfig.
Hope this helps!
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
Hello! I'm Rayen, a product manager at Atlassian. My team and I are working hard to improve the trial experience for Jira Software Cloud. We are interested in talking to 20 people planning t...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs