Expandable block not usable in automation

XMLWordPrintable

    • Jira Software

      Summary

      When configuring a Jira Automation rule to set the Description field using classic Atlassian wiki markup, {expand} macros are not rendered in the resulting issue.

      Instead of creating a collapsible "Expand" block, the issue shows the literal macro text:

      {expand:title=Use Case I}
      Use Case I
      Use Case 1: [Title]
      Description: Provide a summary of the scenario being tested.
      Detailed Requirements:
      Test Case(s)
      Test Case 1 [Title]
      {expand}

      This breaks documentation/test-case templates that rely on expand sections and contradicts Atlassian's own guidance that Automation can populate wiki-markup fields when the field renderer is set to "Wiki style".

       

      Steps to Reproduce

      In Jira Cloud, ensure the Description field for a project (e.g., ADS) is configured to use Wiki Style Renderer.

      1. Go to Project settings → Automation (project-level automation).
      2. Create a new rule:
      3. Trigger: Issue created (or any trigger).
      4. Action: Create issue (or Edit issue fields on the triggered issue).
      5. In the Description field of the action, paste the following classic wiki markup:

       

      [Docs360: Writing Use/Test Cases for QA in Jira|https://nam04.safelinks.protection.outlook.com/\?url=https%3A%2F%2Fportal.us.document360.io%2Fc6092c90-a857-4ce8-8ed3-5328d1832d6c%2Fdocument%2Ftechnology%2Fview%2Fa192bdc8-073c-4df7-9e51-3354a31a4d23&data=05%7C02%7Camatejka%40ugafinance.com%7C84ee4ab908b84c2ef3da08de805af705%7Cd42a452b6ebb49c4b03c3ab702bd4227%7C0%7C0%7C639089325346978909%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=YVVf7s421nCCg9UqZxCHNfbHaID%2BAuPr1K8exqkhzCk%3D&reserved=0]
      Merge Request:
      Please follow the steps detailed in Use Case 1 and 2 below. Any questions or issues encountered should be posted in the comments section below. The QA tester should also provide a comment once testing has been completed.
      {expand:title=Use Case I}
      
      Use Case I Use Case 1: [Title]
      *Description:* Provide a summary of the scenario being tested.
      *Detailed Requirements:*
      #
      
      Test Case(s) Test Case 1: [Title]
      #
      {expand}
      Publish the rule.
      Trigger the rule by creating an issue.
      Open the resulting issue and view the Description.
      

       

      Expected Result

      The Description is rendered using the Wiki Style Renderer, and:

       

      {expand:title=Use Case I}…{expand} produces a collapsible Expand section titled "Use Case I".
      Headings (h2., h3.), bold (*text*), and numbered lists (#) render properly.
      

       

      The created issue looks the same as if a user had manually typed/pasted the same wiki markup directly into the Description field of the issue and saved it.

      Actual Result

      The created issue displays the literal macro text instead of an Expand section, for example:

      {expand:title=Use Case I}
      Use Case I
      Use Case 1: [Title]
      *Description:* Provide a summary of the scenario being tested.
      *Detailed Requirements:*
      Test Case(s)
      Test Case 1 [Title]{expand}

      (!)No collapsible section is created.

      Classic wiki markup syntax is not interpreted, despite the field being configured with Wiki Style Renderer and Atlassian documentation stating that wiki markup can be injected via Automation (e.g., using {panel} etc.).

              Assignee:
              Unassigned
              Reporter:
              Mario Corona
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: