I'm trying to embed a Jira issue in a Confluence document, but the format is really wonky. Other Jira issues that I've embedded the same way (with "/jira") have worked fine.
Here's what it looks like, with proprietary info redacted. I've updated the title on the Jira issue to remove special characters; the redacted portion contains alpha characters only.
What could be causing the line breaks?
Hello Kay,
Welcome to Atlassian Community. Nice to meet you!
I don't know anything off-hand that would cause that. I want to confirm; you have working Jira macros on the same page, and there are also special characters in the title? Are they all single-issue macros? Are they placed on a table?
Can you confirm if the page uses the new editor? Refer to Convert pages to the new editor if you want to see how to tell if a page uses the new editor.
I look forward to hearing from you!
Take care,
Shannon
Thanks for taking a look, Shannon!
"you have working Jira macros on the same page?" yes
"Are they all single-issue macros?" yes
"Are they placed on a table?" no
"Can you confirm if the page uses the new editor?" yes
II saw this problem in a bigger document I created a new one to try to isolate / troubleshoot it. The format is:
text
/jira macro, linked to single issue - format looks correct
text
/jira macro, linked to single issue - format is as above.
"there are also special characters in the title?"
This issue originally had special characters in the title (part of the title was in curly brackets "{...}"), but I updated the title to eliminate the special characters, and the format issue still occurred. It does NOT happen with another embedded Issue with curly braces in the title.
Here's a more complete screenshot in case it helps, with proprietary info redacted again:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ooh, here's another clue. I just mentioned that same Issue in the description of another Issue in Jira, and the same weird formatting appears there:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Kay,
Thank you for sharing those examples with us. I haven't seen this before, and I would like to look at the individual Jira issues to find out what's going on.
Can you report this to your administrator? They can raise a ticket with Atlassian Cloud Support, and we can have a look at your site directly.
Thank you!
Shannon
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.