NOTE: This bug report is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding bug report.

      Summary

      1. Installing Service Desk will create several custom fields (ie. Customer Request Type, Request participants, etc. When the default language is English, these custom fields will be created in English (name and description). When the default language is another language, these fields will be created in the said language. For example, French would be Participants à la requête and Type de requête client.

      However, after it is installed, the name and description will not be updated accordingly if the default language is changed. When originally installed in French, the fields will retain their French name and description even though the default language is changed to English

      Steps to Reproduce

      1. Change default language to French
      2. Install Service Desk
      3. Check the custom fields page to see the names/description created in French
      4. Change the default language to English

      Expected Results

      1. The name and description is automatically translated to English

      Actual Results

      1. The name and description remains in French

      Workaround

      Change these values directly from the database in the customfield table.

      As many of the custom fields created are system fields, they will be locked. This will require to unlock the fields prior to editing them as outlined within the Unlock a locked Jira Software custom field article.

            [JSDSERVER-2326] Service Desk custom fields not able to be translated accordingly

            Antoine [Klee Group] added a comment - - edited

            Seems that this issue still has not been fixed. Note that it therefore conflicts with some apps like Project Configurator, forcing the user to manually translate the problematic Jira service desk fields in the XML file prior to import.

            Antoine [Klee Group] added a comment - - edited Seems that this issue still has not been fixed. Note that it therefore conflicts with some apps like Project Configurator, forcing the user to manually translate the problematic Jira service desk fields in the XML file prior to import.

            Jozsef Lehocz added a comment - - edited

            Please add these missing translations to the HU language pack as well. Thank you

            Jozsef Lehocz added a comment - - edited Please add these missing translations to the HU language pack as well. Thank you

            Simonas Jutkevičius added a comment - Hi, Unlock these custom fields like described here https://confluence.atlassian.com/jirakb/how-to-unlock-a-locked-jira-software-field-779158866.html Edit / Translate them here https://veiklos.vu.lt/secure/admin/ViewCustomFields.jspa Lock them back.

            Hi,

            We would have translations for the Service Desk and the Agile custom fields (or to be able to translate them).

            We would like that the translations to be shown accordingly to the user profile language (on multi language environments, having users using different languages in the world)

            Best regards

            Robert Mota added a comment - Hi, We would have translations for the Service Desk and the Agile custom fields (or to be able to translate them). We would like that the translations to be shown accordingly to the user profile language (on multi language environments, having users using different languages in the world) Best regards

              Unassigned Unassigned
              ywoo Yit Wei
              Affected customers:
              74 This affects my team
              Watchers:
              44 Start watching this issue

                Created:
                Updated: