Low Issue Summary
Jira macro does not work properly within a dynamic macro.
Steps to Reproduce
- Create a Confluence Connect app
- Set up a dynamic macro with a rich-text body and block outputType that renders the contents of it body out using the contentbody/convert REST API
- Install the app into Confluence
- Create a page with the dynamic macro in it, and place a "Jira" macro in the body of that dynamic macro
- Place another Jira macro outside the dynamic macro
- Observe that the "Jira" macro fails to load when within the dynamic macro
Expected Results
Jira macro will display like usual
Actual Results
The Jira macro fails to load. Some macro shows a refresh spinner continuously spinning. Others state that refresh did not work.
If the display option is set to single issue only, the issue type icon is not rendered properly and is just displayed as a spinner.
Notes
- Can be replicated in the old editor
- Used to work before. The first record of occurrence was 2nd of March
- Seems to work fine with outputType inline
Workaround
Currently, there is no known workaround for this behavior. A workaround will be added here when available.
- is related to
-
DEVHELP-2347 Failed to load
- relates to
-
JST-456374
You do not have permission to view this issue
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[CONFCLOUD-65773] Jira Macro does not render inside a 3rd-party macro
Hi there, it seems that the fix released this week didn't fully fix the issue. Sorry for the delay, I'm reopening this so I can continue investigating. Will keep you updated.
This is still not resolved for us at Priceline. Any updates would greatly be appreciated!
After testing this, one of the issues seems to be resolved, on some of my instances but not on others, but the issue of the Jira Issue Macro not loading when there is multiple issues selected (so the table view) is still there for all my instances.
Is this change still in the process of being rolled out and is there any changes the apps need to include to make the table view work?
Thanks,
Josh
This has been resolved now. marc.hanley, tim1512534419 can you please test it.
As users of the Macro Toolbox add-on, we are also being heavily affected by this issue, as we frequently make use of the Heading Expand/Collapse macro in order to improve the user experience. Would we be able to get an ETA on a fix?
FYI akassab:
This issue is blocking support for the GDPR changes for a number of apps including:
- Macro Toolbox
- Navitabs
- Composition Tabs & Page Layout
Our current workaround is to set the gdpr flag to false.
An updated fix has been merged today and is awaiting release.