Uploaded image for project: 'Jira Align'
  1. Jira Align
  2. JIRAALIGN-4296

Description in Epic Status Report not rendering rich text

XMLWordPrintable

    • 1
    • Severity 3 - Minor
    • No

      Issue Summary

      This is reproducible on Data Center: (yes)

      Rich text is not being rendered on the description field for Epics coming from Azure DevOps (ADO)

      Steps to Reproduce

      1. Create an Epic on ADO and fill the Description field using rich text formats 
      2. Sync to Jira Align
      3. Access the Epic Status Report and notice that the Description field will show the HTML tags instead of showing only the formatted text

      Expected Results

      Description field displays the whole text, rendered

      Actual Results

      Description field displays the HTML tags

      Workaround

      Currently, the workaround would be clear all types of rich formatting on the description field of the epic on ADO, however, this is not the best scenario for clients to operate

        1. image-2022-07-25-10-55-39-554.png
          1.08 MB
          Alessandra Garcia

          Form Name

            [JIRAALIGN-4296] Description in Epic Status Report not rendering rich text

            Gaj Umapathy added a comment -

            This bug seems to have resurfaced on 10.131.3 and 10.133.3. 

            Gaj Umapathy added a comment - This bug seems to have resurfaced on 10.131.3 and 10.133.3. 

            Kyle Foreman added a comment -

            Hello,

            This issue is now fixed (as of the release version on the ticket above). Please let us know if you have any questions!

            -Kyle

            Kyle Foreman added a comment - Hello, This issue is now fixed (as of the release version on the ticket above). Please let us know if you have any questions! -Kyle

              kforeman@atlassian.com Kyle Foreman
              cb9f299998cb Alessandra Garcia
              Affected customers:
              1 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: