Hi,
I've written an automation rule that writes specific requirements in the description field - highlighting certain 'code' lines using the monospace formatting. The Wiki editor of the description field front end calls the formatting 'code'. When I use the backtick `to surround the intended words in the automation rule, it does not apply the markdown. It merely surrounds the text with the `. The specific code lines starts and or ends with a special character so I went as far as applying the escape \ but that still does not apply the intended formatting when the automation runs. If I manually enter the backticks on the description field of the ticket afterwards, it applies the monospace/code format.
What do I need to add in the description field within the automation rule to get this to show correctly in the Jira ticket?
E.g.
${appName}
<repo name>
To apply the monospace / code format
Please try using the {code} formatting notation in your rule:
https://jira.atlassian.com/secure/WikiRendererHelpAction.jspa?section=advanced
If that does not help, please post an image of your complete rule and audit log details showing the rule execution. Those may provide context to help explain the symptom. Thanks!
Kind regards,
Bill
I tried that too however it is a code block with line numbers and not what we require - we merely require the monospace/code formatting on specific text between other non formatted text, applying the {{code}} is the same as surrounding the text with 3 backticks '```'.
When applying the single backtick for monospace, all it does is render it like this in the description field:
`${appName}`
I also then receive a successful completion of the ticket automation in the audit log. The audit log below is me testing to add it to a ticket after the fact as I don't want to recreate a new ticket and fill in the description field each time - either way, adding to the description field is the same in create or edit an issue
And this is what it does on the ticket itself (i've just redacted the actual description field for IP reasons. If I manually go and add those backticks to that text, the moment you add the last backtick, the monospace format is applied but only on the front end of the description field not via automation rule.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sorry, I am out of ideas on this one. Perhaps ping the support team to learn what they suggest: https://support.atlassian.com/contact/#/
In my experience, not all Description field macros / formatting can be done in automation rules. My hypothesis is there's more information "behind the curtain" which we do not have access to modify with automation rules and / or the smart value parser takes precedence over the markup parser.
I also tried the {noformat} and {{monospace}} ones, and I found the first works the same as {code} (adding line numbers now) and the second no longer works with the "new issue view".
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.
Hi, any insight you could perhaps provide me here? It would greatly be appreciated!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Moving this to a Jira forum.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.