will there be an impact if custom fields are made in different language?

[shiva]

Jira supports many languages and how it impact if the custom field change to other language after creating custom field. Can we translate custom filed to other language if required.

[Walter Buggenhout · Accepted solution]

Hi @shiva,

Translating custom field names is not something with a major impact. A custom field has an ID behind the scenes, so the field remains the same.

Just as a best practice tip: be consistent. Jira has a set of system fields that you cannot translate yourself (fields like summary, description, resolution etc). For a consistent UI, try to use the same language throughout all custom fields. If users prefer to work in an English UI, then preferably only use English field names and use the translate option to consistently define (e.g.) to Spanish.

Translation options can be found in the same place where you find the configuration settings of your fields.

There are some limitations worth noting as well:

• Custom fields in team managed projects cannot be translated. Although there is a feature request for that (JSWCLOUD-21418) - team managed projects are designed for use by a single team and assume you can use a single language in your project.
• Translations are limited to the name and description of your custom field itself, not the options of e.g. a select list / radio buttons etc.

Hope this helps!

[shiva]

Hi @Walter Buggenhout

Thank you for the reply..

Another thing I just want to know. Is their an alternate for api user to map custom field instead of name/id

Need suggestions regarding this, it would be great.

Thank You.

Regards

Shiva

[Nic Brough -Adaptavist-]

What do you mean by "alternate for api"?  And how would you expect it to not use the identifier for a field when the id is the thing that identifies a field?