Uploaded image for project: 'Jira Work Management Cloud'
  1. Jira Work Management Cloud
  2. JWMCLOUD-564

Not wanted translation from QA to GQ in portuguese Jira users.

    • 8
    • Severity 3 - Minor

      Atlassian Update - 3rd November 2023

      Hi everyone,

      Thank you for your ongoing patience with this bug.

      Translations in JWM have been inconsistent and sometimes unpredictable for users across the world. In an effort to improve this, we've extended auto-translations to include status so that the entire UI is localised to the selected language. These changes are intended to enhance the user experience, so we won't be reverting them.

      Apologies for not making you aware of this change before we rolled it out - we should have let you know well in advance. We'll be publishing a community article in the coming weeks explaining the change and offering recommendations on how to navigate it.

      In the meantime, please reach out to support to understand how these changes affect you and your team.

      The Atlassian Cloud team

      Issue Summary

      Portuguese language Jira users are facing problems when using status with the QA name, Jira is now auto-translating to GQ(not wanted feature). In Portuguese is called QA too and they do not translate this.

       

      Examples are in the attachments.

      Steps to Reproduce

      1. Changer your Language to Portuguese;
      2. Create and Status called QA in your workflow;
      3. Go to status change in the issue and you will find the status now called GQ instead of QA.

      Expected Results

      Even if GQ is the translation to QA(Quality Assurance means Garantia da Qualidade in Portuguese) this translation is not used and it was not happening before, probably just needs a rollback on it since is a not request/needed feature.

      Actual Results

       

      Workaround

      To address this issue, manually overwrite the name and description for each status in each required language using the translation manager. 

        1. ENGINEER REPLICATE 1.png
          ENGINEER REPLICATE 1.png
          67 kB
        2. ENGINEER REPLICATE 2.png
          ENGINEER REPLICATE 2.png
          127 kB
        3. EXAMPLE 1.1.png
          EXAMPLE 1.1.png
          24 kB
        4. EXAMPLE 1.2.png
          EXAMPLE 1.2.png
          6 kB
        5. EXAMPLE 2.1.png
          EXAMPLE 2.1.png
          171 kB
        6. EXAMPLE 2.2.png
          EXAMPLE 2.2.png
          24 kB
        7. image-2023-10-04-16-57-00-635.png
          image-2023-10-04-16-57-00-635.png
          107 kB

            [JWMCLOUD-564] Not wanted translation from QA to GQ in portuguese Jira users.

            Ben Payne added a comment -

            Hi everyone,

            We will be closing this ticket for reasons explained in the description above.

            Thank you for your continued patience and understanding.

            Ben Payne added a comment - Hi everyone, We will be closing this ticket for reasons explained in the description above. Thank you for your continued patience and understanding.

            We have the same problem in French. some statuses are translated, others not.
            it's very annoying, we are interconnected with Power BI, these statuses are interpreted as new statuses in the reports
            this happened from October 5.
            Was there a release on this date?

            Mélanie Liguet added a comment - We have the same problem in French. some statuses are translated, others not. it's very annoying, we are interconnected with Power BI, these statuses are interpreted as new statuses in the reports this happened from October 5. Was there a release on this date?

            NiYunfan added a comment -

            Some workflow status name were also auto translated into Chinese Simplified but we don't want that.

            For example: Testing being translated to 正在测试

            The workaround works for single status name, but it's difficult to cover all status. 

            NiYunfan added a comment - Some workflow status name were also auto translated into Chinese Simplified but we don't want that. For example: Testing being translated to 正在测试 The workaround works for single status name, but it's difficult to cover all status. 

            Hi!

            Here I have same case. Others fields also were impacted like Review, it is displayed as Revisar if portuguese language is configured.
            Is it possible to report what fields were impacted in this update?

            David Santi added a comment - Hi! Here I have same case. Others fields also were impacted like Review, it is displayed as Revisar if portuguese language is configured. Is it possible to report what fields were impacted in this update?

            Hey everyone, 

            I'm Marcel from Jira Cloud. Jira recently added a number of new auto-translations for a number of statuses for customers who wanted to see statuses in their local language. Several existing statuses do this already (to do, done, in progress etc...), but values were missing for many of the new project templates. I'm talking with relevant teams who were making this change around the best approach to roll this back. 

            In the meantime let me provide you with a couple of other workarounds. 

            1. For the status name being QA vs GQ, you can override this via the translation manager for statuses (See https://confluence.atlassian.com/jirakb/translating-the-workflow-statuses-1188786331.html).
            2. For JQL, unfortunately you will need to use the 'raw status name' or status id for advanced queries. Basic queries uses a picker that shows the translated value (so that should reduce some confusion)

            Marcel Caroly added a comment - Hey everyone,  I'm Marcel from Jira Cloud. Jira recently added a number of new auto-translations for a number of statuses for customers who wanted to see statuses in their local language. Several existing statuses do this already (to do, done, in progress etc...), but values were missing for many of the new project templates. I'm talking with relevant teams who were making this change around the best approach to roll this back.  In the meantime let me provide you with a couple of other workarounds.  For the status name being QA vs GQ, you can override this via the translation manager for statuses (See https://confluence.atlassian.com/jirakb/translating-the-workflow-statuses-1188786331.html). For JQL, unfortunately you will need to use the 'raw status name' or status id for advanced queries. Basic queries uses a picker that shows the translated value (so that should reduce some confusion)

              jseam@atlassian.com Jason S
              c79e6a70f93d Ivan Jose (Inactive)
              Affected customers:
              14 This affects my team
              Watchers:
              23 Start watching this issue

                Created:
                Updated:
                Resolved: