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

Owner names with special encoded characters are not displaying properly in Forecast page

XMLWordPrintable

    • 1
    • Severity 3 - Minor
    • No

      Issue Summary

      Owner names with special encoded characters are not displaying properly in Forecast page.

      Steps to Reproduce

      • Go to Portfolio > Epics
      • Open any Epic from the grid
      • Change the owner to any name having an encoded character like Thomas Münch, where “ü” is encoded ( this owner should be added as a member to the program to see the owner name in Epics)
      • Save&Close the epics
      • Go to Portfolio > Forecast
      • Select Portfolio and PI in Tier1 & Tier2
      • Expand the PI list to see the Epic details.
      • Now the Owner name is displayed as Thomas Münch

      Expected Results

      Owner name with special characters should be displayed the same way

      Actual Results

      Owner name with special characters are displayed with some html characters.

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

        1. screenshot-1.png
          screenshot-1.png
          129 kB

            [JIRAALIGN-4769] Owner names with special encoded characters are not displaying properly in Forecast page

            Christoph Piotrowski [catworkx] added a comment -

            Hi Oleksandr, thanks a lot for clarification and the fast response!

            Christoph Piotrowski [catworkx] added a comment - Hi Oleksandr, thanks a lot for clarification and the fast response!

            Oleksandr Lytvyn added a comment - - edited

            Hello cb5a08e181b9, sorry for the confusion, it is fixed but will be rolled out in 121.0 release

            Oleksandr Lytvyn added a comment - - edited Hello cb5a08e181b9 , sorry for the confusion, it is fixed but will be rolled out in 121.0 release

            Christoph Piotrowski [catworkx] added a comment -

            Hello Atlassian Team, this issue is NOT fixed! Can you pls also always close issue giving a fix version? Otherwise it is really time consuming to verifiy bugfixes, that are perhaps not yet rolled out to our instances.

            Christoph Piotrowski [catworkx] added a comment - Hello Atlassian Team, this issue is NOT fixed! Can you pls also always close issue giving a fix version? Otherwise it is really time consuming to verifiy bugfixes, that are perhaps not yet rolled out to our instances.

              dfuller@atlassian.com Don Fuller
              37857daa0c44 Mangala Narayana
              Affected customers:
              1 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: