Uploaded image for project: 'Atlassian Internationalization'
  1. Atlassian Internationalization
  2. I18N-2909

Add translation to the "Organization" and "Request participants" fields

XMLWordPrintable

    • Portuguese (Brazil)
    • Organization

      NOTE: This ticket is for JIRA Service Desk Data Center. Using JIRA Service Desk Cloud? See the corresponding suggestion.

      The fields "Organizations" and "Request participants" are not translated for many languages when you change JSD language settings. Would be good to have this field translated as well in the next versions of JSD Cloud and Server

      Example of impacted languages are (the list is non exhaustive):

      • Portuguese (Brazil)
      • German
      • Russian
      • French
      • Spanish

      Note

      All non-English languages might be impacted by this issue.

        1. fields.png
          fields.png
          75 kB

            [I18N-2909] Add translation to the "Organization" and "Request participants" fields

            DG added a comment -

            It would be very nice if a product owner could be priorise this case

            DG added a comment - It would be very nice if a product owner could be priorise this case

            Gulsum Kurtar added a comment -

            Please add Turkish

            Gulsum Kurtar added a comment - Please add Turkish

            Bartosz Śniadek added a comment -

            Please add the Polish translations.

            Bartosz Śniadek added a comment - Please add the Polish translations.

            Tobias Nilsson added a comment -

            Please add the Swedish translations.

            Tobias Nilsson added a comment - Please add the Swedish translations.

            Lise Wåsjø added a comment -

            Would love to see this fixed in the very near future. It really isn't supporting mulit-languages with these fields being stuck to one language..

            Lise Wåsjø added a comment - Would love to see this fixed in the very near future. It really isn't supporting mulit-languages with these fields being stuck to one language..

            Véronique added a comment -

            Please also add the Dutch translations.

            Véronique added a comment - Please also add the Dutch translations.

            Marie Dautun (Inactive) added a comment -

            pujan.ziaie Thank you so much for sharing your feedback, I understand the frustration. And I do hope this gets prioritised soon. Take care, Marie

            Marie Dautun (Inactive) added a comment - pujan.ziaie  Thank you so much for sharing your feedback, I understand the frustration. And I do hope this gets prioritised soon. Take care, Marie

            Puján Z added a comment -

            Thanks Marie! It seems Atlassian needs better backlog management and prioritization. If the platform claims to support multi-languages, then important fields like Request Participants shouldn't be hard-coded. And if they are, the effort to make them translatable seems minimal to me and shouldn't gather dust for four years. Just a constructive feedback

            Puján Z added a comment - Thanks Marie! It seems Atlassian needs better backlog management and prioritization. If the platform claims to support multi-languages, then important fields like Request Participants shouldn't be hard-coded. And if they are, the effort to make them translatable seems minimal to me and shouldn't gather dust for four years. Just a constructive feedback

            Marie Dautun (Inactive) added a comment - - edited

            Hi pujan.ziaie,

            Unfortunately, it's not about fields not being translated, otherwise the issue would have been solved long ago. Instead, it's about not having access to those strings and therefore having no way to translate them. I haven't looked in details, but typically it's due to strings being hardcoded or not externalised (it can have a variety of other causes). It's a product bug for the dev team to look into. If the bug has been existing for four years, then I believe it's somewhere on their backlog and they haven't prioritised this.

            Marie Dautun (Inactive) added a comment - - edited Hi pujan.ziaie , Unfortunately, it's not about fields not being translated, otherwise the issue would have been solved long ago. Instead, it's about not having access to those strings and therefore having no way to translate them. I haven't looked in details, but typically it's due to strings being hardcoded or not externalised (it can have a variety of other causes). It's a product bug for the dev team to look into. If the bug has been existing for four years, then I believe it's somewhere on their backlog and they haven't prioritised this.

            Puján Z added a comment -

            Four years and still no translation for these two fields? How difficult can it be?

            Puján Z added a comment - Four years and still no translation for these two fields? How difficult can it be?

              agoldthorpe Aidan Goldthorpe
              tsoares Teilor Soares (Inactive)
              Votes:
              111 Vote for this issue
              Watchers:
              69 Start watching this issue

                Created:
                Updated: