Uploaded image for project: 'Confluence Cloud'
  1. Confluence Cloud
  2. CONFCLOUD-77305

Using a "/" in a Custom Jira field will prevent the content of the field to render in the Jira macro in Confluence

XMLWordPrintable

      Issue Summary

      In Confluence Cloud if you insert the Legacy Jira macro and try to display issues that include a custom field that includes a "/" (forward slash) in its name, the content of the field will not show in the Jira macro.

      This is reproducible on Data Center: Not tested

      Steps to Reproduce

      1. Go to your Jira instance and create a customer field for one of your projects.
      2. The custom filed name should include a "/" with no spaces in between the "/" and the words: Pre/Post operational work
      3. Go to Confluence Cloud, select any page, and then insert the classic Jira macro.
      4. Use JQL to locate the project, and then in the display options select the field with the "/" in its name.
      5. Macro will render all the field contents correctly except for the contents of the field with the "/" in its name.

      Expected Results

      Regardless of the name of the custom fields, the contents should be displayed in the Macro

      Actual Results

      The Jira macro will not display the values for the custom fields with the "/" in its name.

      Workaround

      Go to Jira and remove the "/" from your custom field name

      After changing the field in Jira, the macro must be manually updated to reflect the changed field without the slash due to CONFCLOUD-65930

        1. Screenshot 2024-01-05 at 10.58.18 a.m..png
          97 kB
          Diego Peralta
        2. Screenshot 2024-01-05 at 10.58.44 a.m..png
          67 kB
          Diego Peralta
        3. Screenshot 2024-01-05 at 10.59.23 a.m..png
          42 kB
          Diego Peralta

              Unassigned Unassigned
              ebc00f6a1693 Diego Peralta (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: