Formatting changed (/status) when copying from custom field to description of a new issue

[Ross D Webster-Salter]

I have created an automation that generates a new issue in a different project.

Both fields are already configured for Wiki Style Markdown in the render (field configuration). My source issue works well. However, the fields which use the "/status" formatting type do not render well in the destination project.

Source (custom field)

Destination (description field)

[Saurabh Kapoor · Accepted solution]

Thank you for reaching out to the Atlassian support team. I understand that you're experiencing an issue with the formatting of the /status macro when using automation to copy a wiki-style field. This can be frustrating, especially when the formatting is crucial for maintaining consistency across issues.

Based on the information available, it appears that when fields are copied using automation, the wiki markup is formatted according to the wiki renderer, which can lead to changes in the appearance of certain elements, such as the /status macro. Unfortunately, this is a known behavior, and currently, there is no workaround available to maintain the exact formatting of the /status macro when it is copied.

Here are a few points to consider:

• Wiki Markup Rendering: When fields are copied, the wiki markup is rendered, which can alter the appearance of certain elements. This is consistent with the behavior observed in other elements like emojis, dates, and expand macros, which also do not copy correctly.

• Rendering Options: While there are options to render fields as HTML or plain text in automation, these do not specifically address the issue with the /status macro formatting. These options are more suited for fields like descriptions or comments.

• Current Limitations: As of now, there is no specific workaround to preserve the exact formatting of the /status macro when copied through automation. This is a limitation that has been acknowledged, and any updates or workarounds will be documented as they become available.

As I re-searched in the JAC portal, I was able to find the bug logged for this behaviour which is in the Long Term Backlog.

• AUTO-97: When a field is copied using automation, the wiki markup added as the text will be formatted

I'd request you to add yourself as a watcher to the bug report by clicking this link Start watching this issue Jira will keep sending you notifications when any update is posted by our Products Team. To also inform us about how this bug affects your team, please click the This affects my team link.

While I have personally reached out to the Products team informing them about this ticket and how this issue has affected your business, I would really appreciate it if you can also add your comments on the same page. Your feedback is very important to us.

When this bug is in the queue for a fix, the status will change to In Progress, and you will be notified (as a watcher). For additional information on Atlassian's bug-fix policy, please visit this guide.

I appreciate your patience and understanding regarding this matter. Please feel free to reach out if you have any further questions or need additional assistance. We're here to help!

[Ross D Webster-Salter]

Thank you for the detailed response, I will watch the issue and comment there. It is useful for us to provide consistency and a professional polish to our reports (these are also shared with external service providers so do like the nicer formatting) but will live with the current conversion for now.

[Tomislav Tobijas _Koios_]

Hi @Ross D Webster-Salter ,

I can confirm the same behavior/problem on my instances.

I've tried to search for reported issue on JAC, but didn't have any luck there. Meanwhile, I've reached out to the Support team to see what they'll say.
I can get back with an update as soon as I hear from them.

Cheers,
Tobi

[Ross D Webster-Salter]

Thanks a lot, good that it is reproduceable :) appreciate you reaching out.