Is there any timeframe when Markdown is supported in automation rules creatign sub-taks with bodies?

Thorsten Schöning

Hi everyone,

I'm using automation rules to create subtasks with lots of textual description and regular fall back to the behaviour to simply using Markdown within those descriptions. That isn't supported yet, so Markdown is rendered as text 1:1 in the created subtask. Some sort of Jira Wiki markup is supported, but only partly as well.

The AI sometimes suggests things like {{code}}foobar{{code}}, but that fails, because it's interpreted as smart value instead. Then it suggests to escape things like {{ "{{" }}code{{ "}}" }}foobar{{ "{{" }}code{{ "}}" }}, which fails as well, because the parser doesn't support that. It makes the entire subtask creation action fail with a VERY unhelpful error message about fields can't be found in the project and stuff.

None of that would be a problem if simply Markdown was supported somehow. So, are there any plans to fix this? And maybe make the error check for rules check the description as well for syntax errors like above?

Thanks.

Anwesha Pan

Hi @Thorsten Schöning

Your frustration is completely understandable. Below are some workarounds you can follow:

1. Use Single-Brace Wiki Markup for Code Blocks: For multi-line code blocks, use single-bracket {code} or {noformat} tags instead of double braces

{code:javascript}

const greeting = "Hello World";

console.log(greeting);

{code}

2. Pass Native ADF via the "Additional Fields" (JSON) Box: If you need rich formatting (tables, status lozenges, callouts, markdown-like structures) without parser collisions, bypass the basic text box entirely and pass ADF JSON in the Additional fields section at the bottom of the "Create sub-task" action:

{

"fields": {

"description": {

"type": "doc",

"version": 1,

"content": [

{

"type": "paragraph",

"content": [

{

"type": "text",

"text": "Here is the subtask description with inline ",

"marks": []

},

{

"type": "text",

"text": "code snippet",

"marks": [{ "type": "code" }]

}

]

},

{

"type": "codeBlock",

"attrs": { "language": "bash" },

"content": [

{

"type": "text",

"text": "npm install && npm test"

}

]

}

]

}

}

}

3. Escaping Literal Double Braces in Automation Text: If you need to output literal {{ and }} in your description text, use a smart-value variable definition or character codes:

• Define a rule variable:
  • Variable Name: openBrace | Value: {
  • Variable Name: closeBrace | Value: }
• In your description: {{openBrace}}{{openBrace}}my_code{{closeBrace}}{{closeBrace}}

Hope this resolves your issue. 🙂

Thanks,
Anwesha