We have configured application link between our JIRA system (6.1-OD-04-1 version) and Bamboo (4.4.8-od1 version) so associated JIRA issues are displayed in the build details. Mos of the time, this funcionality works fine. But sometimes, the "Could not obtain issue details from JIRA" message appears in the Summary column (last time it happend on 5th August). The link to issue in Key column is correct. We didn't change anything in our JIRA or Bamboo configuration in the meantime.
Do you ever notice such a problem? How to eliminate this?
The exact cause is difficult to determine - but in general, its a timeout problem (after 10 seconds) between the two applications.
When this happens, check the performance/availabily of the application that isn't responding. In most cases, refreshing works. If the issue persists, I recommend looking into network latency.
These questions may help narrow down the problem:
The output of a TCP (not IGMP) trace-route from your computer to your OnDemand instance.
$ sudo tcptraceroute -l 2800 example.atlassian.net
$ sudo traceroute -T example.atlassian.net 2800
Hope this helps!
I'm not sure if we understand each other ;)
Sometimes during our Bamboo builds JIRA issues are not linked and those links are never corrected - each user who checks Issues tab, gets "Could not obtain issue details from JIRA" message (JIRA and Bamboo pages are working as usual).
If really timeout occured during the build, shouldn't Bamboo update links to JIRA issues later?
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
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