Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-43381

Workflow diagram states are not translated

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Low Low
    • None
    • 6.3.12, 7.1.1, 7.1.8, 7.3.0, 7.3.4, 7.12.3, 7.13.1, 9.4.0, 9.12.13

      Summary

      The workflow diagram does not utilise user provided translations for issue statuses.

      Environment

      JIRA Standalone instance.

      Steps to Reproduce

      1. Create a a new project, for example Scrum Software Project.
      2. Create Translations for the workflow for a specific language from: Admin Cog > Issues > Statuses > Translate Statuses
      3. Create an issue.
      4. Using a user logged in using the language that the workflow statuses were translated into, access the issue.
      5. Observe: When accessing the Workflow Diagram of an issue, the digram presents the workflow statuses in their original language.
      6. Observe: Other parts of the UI are using the correct translated statuses (such as the issue browser).

      Expected Results

      The Workflow Diagram should display the translated status.

      Actual Results

      The user does not see the translated statuses in the Workflow diagram.

      Notes

      This was tested with a custom workflow, and a Out-of-the-box workflow (JIRA Scrum Project) in JIRA 7.1.1 with the same results. The Workflow Diagram always displayed the original workflow status when the translated status was expected.

      Original Bug Report

      states are initially created in German language and are translated via Administration > Issue Attributes > Statuses and option "Translate Statuses" in English (p1.).

      If we are logged in jira with user, who has profile set to English (UK) language (p3), we are NOT seeing translated statuses in workflow diagram in English(UK) but in original German language (p2).

      NOTE: Transitions used in workflow are correct visible in English.

      Workaround

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

        1. p1.PNG
          p1.PNG
          29 kB
        2. p2.PNG
          p2.PNG
          12 kB
        3. p3.PNG
          p3.PNG
          13 kB

              Unassigned Unassigned
              48ee737175e5 Marko Haložan
              Votes:
              121 Vote for this issue
              Watchers:
              96 Start watching this issue

                Created:
                Updated: