Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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

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.

1 answer

1 accepted

0 votes
Answer accepted

Hi @shiva dare to live,

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.

Screenshot 2021-04-30 at 09.28.10.png

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!

Hi @Walter Buggenhout _ACA IT_

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.



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?

Suggest an answer

Log in or Sign up to answer
Site Admin
Community showcase
Published in Marketplace Apps & Integrations

Staying organized with Jira: best practices for a better project management

Project managers know this problem: A “mountain of work” lays in front of you, and you don’t know how and where to tackle them. Different to-dos lie ahead, but just one task after the other can be ha...

242 views 2 1
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you