Ok, so the source tab is appearing and we've had no issues up to now - though I don't know if this has been around for a while.
When I view an issue, I see all 14 of the changesets that have been committed to our SCM (Mercurial) for it. However, a number of users are only seeing 8. I thought it was maybe a timeout issue, but if I SU to one of their usernames I get the same problem.
Sorry if this has already been asked, I've searched and found nothing:(
what authentication method are you using for your application link between FishEye and JIRA?
If you're using OAuth or Trusted Applications, please check whether the FishEye user corresponding to the JIRA user viewing the source tab has the permisisons to see all the commits. Can the user search for all the commits in FishEye directly (try searching for the issue key in FishEye's quick search field)?
Thanks for answering so quickly!
We are indeed using Trusted Applications. The changesets are visible by all the users and bizarrely searching for the issue key brings up 8 matches, but a different set to the ones displayed in Jira. If I give them one of the missing links they can navigate to it straight away.
Just to let you know FishEye 3.3.3 was released today, it contain the fix for https://jira.atlassian.com/browse/FE-5126which you might be affected by. Would you consider upgrading your instance to see if that helps?
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
👋Community members! Downtime happens. And great incident response takes a village. Teams like Support, Dev, SRE, Ops, IT, and Marketing have to come together to resolve the problem while keep...
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