By default, the timer is set for processing of smart commits every 60 minutes.
To use this feature:
Resource materials:
https://confluence.atlassian.com/display/AOD/Processing+JIRA+issues+with+commit+messages
https://confluence.atlassian.com/display/JIRAKB/DVCS+smart+commits+do+not+work
Hope this helps.
Thank you for your answer!
Is there anyway to change the default processing time?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
+1
Every 60 minutes is far too frequent when it currently takes 2-3 hours to sync!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can change the delay / interval by editing com.atlassian.jira.plugins.dvcs.scheduler.DvcsScheduler:job on <your-jira-url>/secure/admin/ViewServices!default.jspa
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If you have webhooks installed, then you should see updates coming through within minutes of the action taking place in GitHub. The periodic syncing that the DVCS Connector does (once per hour) is just a backup measure incase the webhooks fail.
In case of slow refresh times the problem may actually be that your webhooks did not install correctly. See the following KB article:
https://confluence.atlassian.com/display/JIRAKB/Slow+Appearing+Commits+from+BitBucket+or+GitHub+in+JIRA
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.