So why does the Jira Issue Macro only show in Editor but it lists out a URL (that doesn't have the macro description of the actual issue) when viewing the saved version of the document? I find this extremely annoying. I converted to the new editor, then had to update all my links using the new editor programming, and now that I converted to the new navigation, it doesn't show the links at all just the URL. This is creating more work and providing less functionality. Am I doing something wrong? Otherwise, I'm not impressed with this feature in the upgrade.
Hello @Mindy_Buss !
By reading your issue I understand that Jira Issues are not displayed as expected when using the Jira Macro in Confluence. This seems to affect pages migrated from tinyMCE into Fabric.
With this in mind, I tried to replicate the behavior in my Confluence Site.
I first tried to achieve that with the list view of the macro:
In edit mode:
In view mode:
In both cases, the issues are displayed as expected. Then, I tried to replicate that by selecting the Single Issue display mode. Again, the behavior is what is expected from the macro:
In edit mode:
In view mode:
And lastly, I pasted an issue link straight into Confluence while editing. The issue displays as expected too:
In edit mode:
In view mode:
With the results above, I would like to ask you some questions:
- Is this happening only in pages that have been converted from the Legacy Editor (tinyMCE) or is it present in newly created pages that use the New Editor (Fabric)?
- Are you using the list or single-issue view in Jira Macro?
- What happens if you pasted a single issue in Confluence?
- Could you share screenshots with the behavior with us?
When sharing screenshots, take care not to disclose sensitive information with it. Our community is open and everyone can see everything posted here.
Looking forward to your reply!
Thank you for your detailed response, and I appreciate your assistance.
- Mindy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Also, I had my IT guy look into it and this is what he said:
It looks like the Table Filter macro is the cause, somehow it interferes with the table. Unfortunately, there is no way to solve the problem by ourselves as we use JIRA Cloud. They have to update the macro to work with the updated Confluence site.
Please advise.
-Mindy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello again, @Mindy_Buss ! Thank you very much for gathering more information around this behavior.
Looking at our historic reports, I was able to find one that has been closed due to the fact that it was not possible to replicate.
Here:
I wonder if there is anything in common between the links that are not converted. The same question goes for the Jira Issues that are correctly converted.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.