How long should OnDemand smart commits take?

[Dan Fabulich]

I'm testing smart commits with Bitbucket and JIRA OnDemand. Twenty minutes ago, I pushed a commit to Bitbucket referencing a JIRA. I see the commit on Bitbucket.org; it links to JIRA correctly. But on the JIRA side, the issue is still open and there's no link back to the commit.

How long should I expect this to take? Are 20 minute delays normal? At what point should I contact support? (FWIW, smart commits clearly are working at least sometimes.)

[Abdulrazaq Mohammed Ali Omar · Accepted solution]

Hi Dan,

Typically once the commit shows on your JIRA ticket, the smart commit should take effect. If it takes longer than that you should check your Email configuration on your local git/Hg client, where your Email address should be the same as your Jira user Email address for the smart commits to work, you can reference here:

-https://confluence.atlassian.com/display/ONDEMANDKB/Git+Smart+Commits+are+not+working

Hope it helps

[Dan Fabulich]

That's not the question I'm asking. You're talking about the case where a commit shows on the JIRA ticket but doesn't mark the issue as resolved. I'm talking about pushing commits to Bitbucket and not seeing the commit on the Commits tab in JIRA. After a long enough wait, (half an hour or more) the commit appears on the Commits tab and resolves the issue at the same time. How long should I reasonably expect to wait for JIRA to detect a Bitbucket commit?

[Abdulrazaq Mohammed Ali Omar]

It does not take that much for sure. It usually takes up to 2 minuts max. But this would be an interesting case with support. I'd suggest to log a ticket on our support channel : support.atlassian.com and am sure someone will take a look at the problem.

[mhottinger1]

Dan – Did you happen to figure out what was causing the delay? I'm experiencing the same issue with an on-prem instance of JIRA. Right now I'm sitting at a 35+ min delay between commit and Smart Commit changes being reflected. Not ideal.