Jira Issues Macro not working - content rendering

[David Dube]

Background:

We have a Jira On Demand Instance, and an internal instance of Confluence running 3.5.1.

We had been pulling our content from our Jira On Demand Instance into our Confluence instance using the jiraissues macro w/no issues. Unfortunately, the content is no longer being pulled... the macro appears to just sit there with a "Processing, please wait..." indicator

Sample code of jiraissues macro instance (I obfuscated username, password, and specific doman)

{jiraissues:url=https://ourjirainstance.jira.com/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?jqlQuery=project+%3D+%22CSC+Universal+Binary%22+and+%22Issue+Source%22+%3D+%22User+Acceptance+Test%22+and+%22Reported+Version%22+%3D+%22Version+3.2%22+ORDER+BY+status+ASC%2C+key+DESC&tempMax=1000&os_username=omited&os_password=omited|columns=key;priority;summary;reporter;assignee;reported build;status;created;updated}

Thoughts? This was working fine... someone most have been tweaked in one of the Jira OnDemand updates???

[Jackson Harper]

Aimir CG is an architectural visualization company based in China, delivering consistent art quality 3D interior rendering services and animations worldwide. We are fast, efficient and always deliver on time. Our professionalism and communication skills make us easy to work with and the end product was nothing short of impressive!

[David Maye]

It sounds like the JIRA issues aren't able to be pulled into Confluence. I'm not sure what your JIRA/Confluence settings are, but this bug ticket may be related:

https://jira.atlassian.com/browse/CONF-31663

Otherwise, usually a spinning icon means that the macro finds the JIRA issue, but seems to get stuck grabbing the data (for whatever reason). If you're on a self hosted Confluence server, I would suggest either rebooting the server or disabling/re-enabling the JIRA Issues module and see if the issue persists.

[EddieW]

You may need to dig into the logs, could be a connection timeout. You can enable DEBUG logging on the plugin specifically if needed, though I suspect there should be something already.

Check the Application Link configuration in Confluence and validate overall connectivity. (You could also try using CTRL+SHIFT+J while editing a doc to test)

If that works try using a filter in JIRA that returns a small result set (a few issues), and see if the result differs.

Also I had an issue specifying fields once, and if I just left it empty the macro worked, so you may give that a shot.

[David Dube]

I tried two tests... 1) I constrained the search to pick up a unique jira ticket (based on a defined issuekey) and it continues to spin. 2) I then took the above example, and removed all explicit columns, and again, I continue to see the spinner...