It looks that in the newer versions of Confluence (like 7.3.1) JIRA issues are loaded by the browser asynchronously. In some older versions, like in 5.6.3 the macro seems to load the issues synchronously. Is there a way to switch the macro into the synchronous mode for backwards compatibility?
The reason is that we are using a macro that takes the result of JIRA issue macro and process it. However, it is a server-side macro, so it needs the data synchronously.
So, currently I see that in preview mode everything loads and gets processed ok, but in display mode I see no data from JIRA issues / filter (only column names)
From a glance, this appears to be similar to the issue, described here: https://community.atlassian.com/t5/Answers-Developer-Questions/Make-JIRA-Issues-macro-loaded-synchronously/qaq-p/468447
Any ideas would be appreciated
let me put it in another way:
1. there is a server-side macro (the outer macro)
2. the outer macro has an inner macro which loads data asynchronously (like JIRA issues/filter)
3. I'd like the outer macro (being processed on server's side Java) to get all the async data from the inner macro
How this could be achieved?
The switch to browser-loaded issues was done primarily for performance reasons. It results in a faster pageload for the user accessing the page (as the rest of the page can paint in the browser while the issues are still being returned) and prevents bottlenecks on the application server side so a slow-loading query can't bog the Confluence server down for everyone. Short of holding back on to a particular version of Confluence, there is not a way to force the macro to load synchronously.
You might have a couple options:
We also have a dedicated Developer Community that might be good to check out for plugin development related questions. Since the topics are more focused, it's easier for other developers to watch the questions coming in and provide guidance.
Daniel | Atlassian Support
Daniel, many thanks for your response!
May I know on which version of Confluence the switch to browser has been done? At least I'll be able to document the compatible versions.
Also, since I see in the preview everything works fine, is there a way for the outer macro to pretend it is always working in the preview mode (or it would be a bad practice)?
Or, there might be a way for the outer macro to process the async part (browser requests) on server side?
Hey there, folks! For most of us, the past six months- yes, you read that right- have been a journey. More people than ever before have pivoted to working remotely, and navigating being on-scre...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events