-
Bug
-
Resolution: Cannot Reproduce
-
Low
-
3
-
Severity 2 - Major
-
0
-
Issue Summary
Jira issues when converted from legacy editor show as 'Data Card - Link' in the new editor
The Jira issues are rendered properly in the new editor after conversion. However, this is causing issues with the 'Page Properties report' macro, where this Jira shows a normal link instead of a card.
However, if we replace this 'data link' (Jira issue converted from Legacy editor) as a Jira issue on the 'Page Property' macro. We are able to see the Jira issue as expected in Page Properties Report macro.
Steps to Reproduce
- Create a page in legacy editor
- Add Page Property macro and add the Jira issue inside the table - (Page 1)
- Create another page with Page Property Report macro - (Page 2)
- The Jira issue on Page 2 looks as expected at the moment.
- Convert Page 1 to the new editor.
- Check Page 2 and now we'll see the Jira issue displayed as a normal URL, not a card.
Expected Results
The 'Jira issue' in the legacy editor should get converted as a 'Jira issue' on the new editor.
Actual Results
The 'Jira issue' in the legacy editor is getting converted to a 'Data card link' in the New editor.
Workaround
Manually replace 'Data Card link' with a 'Jira issue' after converting Page 1 (Page containing Page Property macro). Now it shows as expected on Page 2 (Page containing Page Property Report macro).
Replacing multiple issues in multiple pages is not a viable solution and hence this issue needs to be addressed.
- is related to
-
-
- Closed
-
- mentioned in
-
Page Failed to load
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[CONFCLOUD-72781] Jira issues when converted from legacy editor show as 'Data Card - Link' in the new editor, this affects Page Properties Report macro
Hello 13f27f9b2775 and everyone,
This is Mariia from the Confluence team. Thank you for raising this bug and bringing it to our attention. After our investigation into this issue, we weren’t able to reproduce the behavior according to provided steps to reproduce within our instances. If this issue still reproduces, please contact and provide detailed steps with example pages.
We will keep this issue open for another 14 days, but if we don’t hear back by then we will need to close this out to focus on our upcoming roadmap for all Confluence users.
Best,
Mariia
Hi everyone,
This is Oleksandr from the Confluence team. Thank you for previously raising this bug and bringing it to our attention.
Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Confluence users.
As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know by posting a comment and we will review.
Thank you again for providing valuable feedback to our team!
Best,
Oleksandr