We have our JIRA instance connected with fisheye. When dev makes push to git, small piece of code "pings" fisheye to scan repository. It takes maybe a minute. This piece of code also forces devs to insert a JIRA key into commit message so fisheye can connect commit with issue. But sometimes it takes ~30minutes to commit be available in a certain issue. Is there any way to make JIRA ask fisheye real time? Or at least force this cache refresh every 5 minutes?
the commits should appear in JIRA as soon as they're indexed in FishEye (so if you see them in FishEye you should see them in JIRA as well). Having them appear only after 30 minutes might indicate a communication issue between JIRA and FishEye, where FishEye can't notify JIRA about new commits.
Please have a look at this knowledge base article, about troubleshooting these issues, and make sure your application links are configured properly. If you're still having problems it'd be best to create a support request, so that our support team can investigate further.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Atlas Camp is our developer event which will take place in Barcelona, Spain from the 6th -7th of September . This is a great opportunity to meet other developers and get n...
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