-
Bug
-
Resolution: Fixed
-
Low
-
5.4.2, 5.4.3
Problem summary
Disabling in-app notifications (or the underlying Workbox plugins) will cause the JIRA Issue dialog to break in a few ways. This seems to be a regression of CONF-30822, originally fixed in 5.4.0
Steps to reproduce
- Set up Confluence 5.4.2 with an application link to a JIRA instance
- Confluence Admin > In-App notifications, and choose to disable in-app notifications
- Add/edit a page and perform the following two tests:
- Click the Insert
sign and select JIRA Issue. Problem 1: Observe "No Macro Metadata" error. Cancel out of this. - Start typing {jir and press enter to bring up the JIRA Issues panel. Problem 2: Observe that the sidebar and insert buttons missing
- Click the Insert
I was also able to reproduce this in 5.4.3.
Workaround
Resolution
This issue is fixed in JIRA Macros 5.5.2, which is compatible with Confluence 5.4 and above. The fix will be bundled in Confluence 5.5.
- is a regression of
-
-
- Closed
-
- mentioned in
-
![[Atlassian Documentation] Page](/images/icons/generic_link_16.png "[Atlassian Documentation] Page")
Page
No Confluence page found with the given URL.
-
Page
No Confluence page found with the given URL.
-
Page
No Confluence page found with the given URL.
-
Page
No Confluence page found with the given URL.
-
Page Loading...
-
[CONFSERVER-32861] Insert JIRA Issues dialog missing sidebar or displaying "No Macro Metadata" error
Thanks a lot for info. I thought Confluence Plugin manager will provide me info about new version is available, but seems it is not a case. It even do not allow me to update the plugin directly from Marketplace. So I have to download it from Marketplace to my computer and then upload it into my Confluence.
Any news when patch will be available for us? This problem really hurts usability!
velias We'll keep you informed when the new version of Jira Issues Macro that contains this fix is uploaded to Market Place.
Did you tested patch of this bug on clustered Confluence also, as it do not support Workbook at all for now?
https://jira.atlassian.com/browse/CONF-27248
I'm facing this bug on Confluence 5.4.3 clustered, no any workaround from KB works for me, so I'm really waiting for this patch.
I think priority is higher than "Minor" for all users of cluster!
@Vlastimil: Yes, this is the behavior for system (aka: bundled) plugins. These are not reported by the plugin manager, if there are newer versions available, even when these are compatible.
As far as I remember this was a deliberate change at some point, because system plugins are not tested against previous versions completely, so upgrading them to a non-bundled version has a certain risk of negatively impacting system stability.