"Could not obtain issue details from JIRA" message appears

Question

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?

Regards,

Dominika

RianA · Answer

Perhaps this thread might help? https://answers.atlassian.com/questions/34798/jira-ticket-details-are-not-listed-in-bamboo-plan

D.Waligora@lgbs · Answer

Jason,

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?

Regards, Dominika

AgentSmith · Answer

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: * Is page load slowness intermittent or continuous? * If intermittent, is there a pattern to the when slowness is experienced? * All OnDemand users or a subset? * Single location or multiple? * Are particular pages noticeably slower? Which ones? * Is is just OnDemand pages or other sites? The output of a TCP (not IGMP) trace-route from your computer to your OnDemand instance. * Windows: (Skip this step if on Windows.) * OS X: Install tcptraceroute (e.g. through Homebrew, MacPorts, etc.) and run: * $ sudo tcptraceroute -l 2800 example.atlassian.net * Linux: Run: $ sudo traceroute -T example.atlassian.net 2800 Hope this helps!