jira development tab cache timeout


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?




1 answer

0 votes
Lukasz Pater Atlassian Team Nov 13, 2015

Hi Marek,

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.

Suggest an answer

Log in or Sign up to answer
Community showcase
Asked Thursday in Jira Ops

I'm John Allspaw, Ask Me Anything about incident analysis and postmortems

I'm John Allspaw, co-founder of   Adaptive Capacity Labs, where we help teams use their incidents to learn and improve. We bring research-driven methods and approaches to drive effective inciden...

5,353 views 21 17
View question

Atlassian User Groups

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!

Find my local user group

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

Groups near you