We have started to use JIRA and now we are trying Smart Commits and it doesn't seem to work. We have done all the steps necessary to connect JIRA with Bitbucket and we have done the commits using Smart commits' syntax.
This is the issue (new feature):
We don't see anything on Comments tabs.
And these are two commits done:
What we did wrong? Why we can see the comments on the issue?
The repository's Smart Commits checkbox was checked before the commit was actually saved.
Can you confirm the repository's Smart Commits checkbox was checked before the commit was actually saved?
What it is a little bit out of the usual standards is using a 10-character project key, but I doubt that's the cause.
Veronique, yes, we resolved it some time ago, but the resolution was very bizarre:
We got into the habit, when commiting with a one-line message to begin it with one or two space, then the Jira ticket, then another 2 spaces for any further Jira identifiers, another 2 spaces and then whatever other message we wanted!
I said it was bizarre, didn't I? :D
It's become such a habit that I don't even know if a recent update fixed any issues and we don't need to do that anymore. It worked so consistently that we just shrugged and it became part of the "WTF" workflow. >.<
So something like:
$ git commit -am '__PROJ-1234__#jiraidfield_some_text__commit_message'
Where every _ stand for a blank/space.
Well, much to our dismay, we just upgraded our Jira instance to the latest one a week or so ago - and now smart commits aren't working anymore either! Application links are all there, the tickmark for Smart Commits is there. But the comments aren't showing up anymore! (Jira IDs are still properly populated in Bitbucket and branches and commits are still properly showin in Jira)
Smart commits aren't working for me on our installed, Jira server v7.1.9.
I've verified that our Webhook with BitBucket is enabled properly since we are able to see Jira Transitions triggering on Bitbucket Pull Requests. It's just the commits that aren't visible, even with the Jira issue properly mentioned in the commit.
Reporting the same issue, I committed the following comment this morning:
API-1 #time 1h Fixed caching mechanism to not store session expired message #Delivered
The issue picked up the comment but the issue was not transitioned to "Delivered" as expected, nor was there any time logged.
+1 Same issue for us. "Smart Commits" does not work using Jira Cloud. It picks up the ID of the issue and connects it to "Commits".
Neither logging work nor transitions get picked up... Tried the "double spaces" trick as well, but no luck.
PPP-123 #time 2h Hunting that bug. #resolve-issue
If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot