Status macro in Markup for Automation not working

Question

I am trying to set a default description field content or template for an automated rule.

I want to add a status macro there but for some reason the macro markup is not working, I am only getting the literal text in the Description field

{status:colour=Yellow|title=post|subtle=false}

Other macros like Panel are working fine. 
___________________

I am following these documentation links:

https://confluence.atlassian.com/doc/status-macro-223222355.html

https://www.cwiki.us/display/CONF54/Confluence+Wiki+Markup+for+Macros#ConfluenceWikiMarkupforMacros-Statusmacro

Does someone know what is happening or how can I achieve what I am looking for?

Thanks in advance.

Bill Sheboy · Answer

In that post example, the Description "template" is added after the issue is created using an automation rule.  And so the flow is probably: create an issue without a Description, wait a second or two, and then immediately edit the issue with the updated template.

Team-managed projects allow setting a default value for a field like Description.

Sorry, I misspoke using that term, instance default.  For company-managed projects, I believe the two work-arounds are to: purchase marketplace addons or use a "shadow field" based on custom fields and workflow changes, as described here: https://community.atlassian.com/t5/Jira-questions/Default-text-for-Description-field-on-Jira-Cloud/qaq-p/785597

Daniel Flores_iw9xk9 · Answer

Hi Bill,

I really would like to know more about these "instance field defaults" since I am not aware of another way to set some default values inside the Description field.

In many places, I've seen the same workaround: using automation.  For example:

https://community.atlassian.com/t5/Jira-Software-questions/Is-it-possible-to-set-a-default-value-for-the-description-field/qaq-p/1739686

Regards,

Bill Sheboy · Answer

Hi @Daniel Flores -- Welcome to the Atlassian Community!

First thing, you note using automation rules to set a default / template for a field.  Automation rules run (i.e. trigger) after something has happened, such as issue create.  They cannot be used to create a field template.  To do that, please change your instance field defaults (or project for a team-managed project), or use a marketplace addon.

Next, in my experience not all of the possible markup for a field like Description can be set by an automation rule.  There is apparently more stored with a field than automation rules can change.  I have even tried this by calling the REST API functions and was unable to reproduce all of the markup.

A similar issue is trying to preserve markup when copying fields, as described in this open defect https://jira.atlassian.com/browse/AUTO-97 and this suggestion for the expand macro https://jira.atlassian.com/browse/JRACLOUD-81703

Kind regards,
Bill