Coming back to this a few years later. New company. Same problem.
But I'm back with a solution that worked for me this time! Combo help between Rovo & Claude.
The description field in Jira Automation is ADF (Atlassian Document Format), not wiki markup. That's the whole problem in one sentence. Typing h1., ##, **bold**, whatever, straight into the Description field just sits there as plain text.
Here's the fix that I found. First, make sure to leave the `Description` field completely blank in the action itself. All of your actual description content goes into the Additional Fields box instead (More options > Additional fields), as a plain wiki markup string:
{
"fields": {
"description": "h2. Problem Context\nSome text.\n\nh2. Next Section\nMore text."
}
}Jira takes that string and converts it into real headings and bold, server side, at creation time. It's the same wiki markup conversion Jira already uses elsewhere (there's a doc on converting wiki markup to HTML for outgoing emails that points at the same underlying converter), just triggered from a different spot than I expected. The two fields fight each other if you fill in both, so the visible Description box has to stay empty for this to actually take effect.
One thing worth knowing if you go this route. Once you've got smart values with quotes in them, the rule editor's own JSON checker may flag the whole thing as invalid JSON. Ignore it. The evaluation happens after Jira resolves everything inside the double curly braces, not on the raw text the editor is linting, and the rule runs fine anyway.
Wish I'd found this a few years ago, but hopefully it saves the next person the wait.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.