Summary

      Wrong description is displayed for issue priority if the user's language is not the instance's default.

      Environment

      Jira Cloud

      Steps to Reproduce

      1. Create a priority with name Blocker
      2. Add a description
      3. Change your profile language
      4. Open https://<YOUR INSTANCE>.atlassian.net/secure/ShowConstantsHelp.jspa?decorator=popup#PriorityLevels
        • You'll see "Blocks development and/or testing work, production could not run." instead of the description you set

      Expected Results

      The value set for description is shown no matter the language set on user's profile.
      Or, the value set on translation is displayed.

      Actual Results

      The default description is displayed.

      Notes

      This is not reproduced will all priorities.

      Workaround

      Add a translation for the impacted priority

            [JRACLOUD-68629] Wrong description is displayed for issue priority

            Monique Khairuliana (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 2513091 ] New: JAC Bug Workflow v3 [ 3356808 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Michael Tokar made changes -
            Resolution New: Duplicate [ 3 ]
            Status Original: Open [ 1 ] New: Resolved [ 5 ]
            Michael Tokar made changes -
            Link New: This issue duplicates JRACLOUD-69797 [ JRACLOUD-69797 ]
            SET Analytics Bot made changes -
            Support reference count New: 1
            Paula Silveira made changes -
            Description Original: h3. Summary

            h3. Environment
            (Optional - If Applicable)
            *
            *

            h3. Steps to Reproduce
            # Step 1
            # Step 2

            h3. Expected Results

            h3. Actual Results
            The below exception is thrown in the xxxxxxx.log file:
            {noformat}
            ...
            {noformat}
             
            h3. Notes
            (Optional - If Necessary)

            h3.Workaround
            (If there is no workaround directly say so)
            New: h3. Summary
            Wrong description is displayed for issue priority if the user's language is not the instance's default.

            h3. Environment
            Jira Cloud

            h3. Steps to Reproduce
            # Create a priority with name *Blocker*
            # Add a description
            # Change your profile language
            # Open https://&lt;YOUR INSTANCE>.atlassian.net/secure/ShowConstantsHelp.jspa?decorator=popup#PriorityLevels
            #* You'll see "Blocks development and/or testing work, production could not run." instead of the description you set

            h3. Expected Results
            The value set for description is shown no matter the language set on user's profile.
            Or, the value set on translation is displayed.

            h3. Actual Results
            The default description is displayed.
             
            h3. Notes
            This is not reproduced will all priorities.

            h3.Workaround
            Add a translation for the impacted priority
            Paula Silveira made changes -
            Description New: h3. Summary

            h3. Environment
            (Optional - If Applicable)
            *
            *

            h3. Steps to Reproduce
            # Step 1
            # Step 2

            h3. Expected Results

            h3. Actual Results
            The below exception is thrown in the xxxxxxx.log file:
            {noformat}
            ...
            {noformat}
             
            h3. Notes
            (Optional - If Necessary)

            h3.Workaround
            (If there is no workaround directly say so)
            Paula Silveira created issue -

              Unassigned Unassigned
              psilveira Paula Silveira
              Affected customers:
              0 This affects my team
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: