If you state that the review would be done in roughly 12 months, we should have been given an update in 2020. Now it's five years later and still there's no update from you.
As an Atlassian Solution Partner consultant I know that more and more customers asking for this functionality and even react with "seriously? why isn't that possible?"
I wouldn't say that this is a bug per se when looking at the date this suggestion was created. However, because applications around the world evolve much faster and from UX perspective though I consider it a bug now because it highly impacts end user experience. Not everyone understands English oder whatever language your custom field options are written in.
Even though you possibly get a translation when user browser built-in functionality this may be blocked by your organisation thus end-users have to work around it.

Oh and if you finally start implementing these translations don't forget to consider translated custom field names and their options when using them in advanced search. At the moment only the custom field default name is used. In basic search you can at least search by the translated custom field name and then switch to advanced search if you don't know the default value as end-user.

Any news ? 

I would also appreciate a status update. This is much needed for our setup to work.

Last update dates from April 16, 2019 with this comment: 

"This suggestion will be reviewed in about 12 months time, at which point we’ll consider whether we need to alter its status."

What is the current status please?

Dear Jira Product Owner:

I was just wondering that this is not possible and see this missing part as a bug and not feature or suggestion. Using list options is core with forms.

If a translated app to users worldwide is provide these translations are mandatory to match UX.  Otherwise users are not able to select the right entries without a dictionary aside. Example: English vs. Mandarin. 

To reenforce the arguement thinking from another perspective: I would assume that all people worldwide are able to use a system with a default language selecting values --> which would lead into "we don't need translations at all" --> which is not the case. 

BR Johannes

"Not being considere" --> I assume this will likely not change since there are several plugins that do this already..

Is there an update on this topic? It's really annoying that you can't translate custom fields. Since 2014, people would like to have this option implemented. The last update was in 2019. There must be a way to translate these fields.

What about JSM data center ? this feature won't be considered for DC ?!

Dear Jira's product owner,

   This improvement would be really helpful and appriciated by us.

Thanks.

WBR,

Evgeniy

Hello everyone

Based on what I see here, I understand that this will not be implemented for Jira Server/DC, but is there a feature request for making it part of the request type translations for the portals? So not on the Jira agents/admin's side of things, but for the portal/customer users? https://confluence.atlassian.com/servicedeskcloud/blog/2017/05/translate-your-customer-portal

Best regards, Maria Heij

We are living in a globalized world and almost every company is acting internationally or is dealing with multilingual people within a country. So this is very weak of Atlasian.

That it is possible to translate everything but these fields is really frustrating. What does a developer think about implementing something like this? That makes no sense at all... First of all it is not even a complex feature to program but still nothing happens since 2014!

If I had known that, we wouldn't have chosen Jira and if that wouldn't be changed, we will have to switch to another service. An app in the Marketplace is of no use to me because it is only for servers and I use the cloud.

Hi All,

Does anyone know if new version of Translate Field Options for Jira app supports existing custom fields (Jira standard custom fields and/or 3rd party app custom fields) or is it still so that this app only works with own custom fields provided by the app. 

Many thanks!  

Thanks for the hint @Matthew Stublefield!

The "included" bit is translating a field, not a field option. There's a gap in the out-of-the-box tool.

@Matthew Stublefield

Thank you for the hint!

It is a helpful solution, but a bit price if since the normal field translations are included.

I just saw that this is not being considered for the roadmap. Since it is solved by a marketplace app, could someone at Atlassian amend the description to point people to that app?

https://marketplace.atlassian.com/apps/1217749/translate-field-options-for-jira?hosting=server&tab=overview

Hi guys

the translation of custom field value is a missing puzzle piece. Especially with Jira Service Desk is is weird to have a custom trasnlated gui, but then the values of a particular field are in english, german or whatever the author was choosing. Having the option to translate values is therefore great. 

Your decision is really very disappointing. We have to maintain 4 languages and with this the use of Jira Service Desk is obsolete. No chance to use this.......

This is absolutely sad and will contribute to even more potential customers deciding against Jira because of its low priority concerning internationalization.

I'm very disappointed. Mainly because your decision comes without any explaination why you won't consider this.

I have to agree with Carmen.

We have to support 3 languages - German, English and Dutch.
I think there will be more languages in future.

For us this decision could evolve into a blocker for us...

I must say that I am deeply disapointed by the decision to NOT consider this change. We are a bilingual cie and this make it hard for us. We have to have French and English for each list value so our list are always long. Any other way of presenting different language doubles everything.

I can't imagine the nightmare for this if you are a multilingual cie

I think so, too. But probably, this suggestion does not have enough visibility at Atlassian because it has only got 179 Votes.

So: If you are reading this and this is still a major thing for you, please share it with your colleagues and customers and ask them to vote.

Hi,

It's a really important feature that can put a stop to the implementation of Jira.

Think of the following cases:

• In multilingual countries like Belgium, Switzerland, Luxemburg... it's always a must for the tools to adapt to everyone's language. In the public institutions it's even required by the law!
• In global companies teams across the world need to collaborate. Not everyone speaks english. And even if someone speaks english it's recognized that you always get a better understanding in your mother tongue. It's often a mandatory requirement.
• ...

Hi, exactly same issue in our company. 

We have many customizations and options are visible in one language only!?!?!? Or as a looooooonnng glued string.

I don't get why Atlassian focus so less on globalisation.

Hi, this is also one of the most wanted enhancements of Jira in my Company. Currently we have to Name the options in four languages.

Hi, guys, any updates on this? I have some users who are rather vocal about having EVERYTHING in the local languages. (That's right, there is more than one and none of them is English!)

At the moment I don't think so. 

Will be the possibility to translate options in customFields created via plugins? I would like to develop plugin which add some selectCFType customField, but for now there is no way to provide translations for options of customField

Hi, about the new version we are working and studying some possibilities, because changing original fields is not recommended. 

Robert, sorry , I don't understand well. What do you mean exactly?

Is there any way to set translations for the select options in the plugin or is planned for future version?

Hi,

when is this next version slated for release?

Thanks Alberto! Sounds great. I wrote you an email

We are working on it.

In the next version, we want to be able to translate all values, not only own fields.  

But it only works with own custom fields provided by the app 

You can use: https://marketplace.atlassian.com/plugins/com.devoog.jira.plugin.translateFields/server/overview

Attach

I am surprised, that this is not possible. It's a must to make custom field options useful.

Hello, the translation would be very useful for us. It would contribute to make JIRA well accepted in our organization.

Even just for column heading on a board... there's no way to display just French or English...

We are in Canada as well and have to create our option in both languages and it is always too long. Same thing for transitions.

We need this as well. Our company has to comply with Canada's official languages act and are finding this to be quite a problem for us. 

This feature is essential for us as well as we are using JIRA for processes that are ISO 9001 certified for which "readability" is a big issue.

We have users in English / French and Chinese across the country and having the ability to have the drop down in the correct language for the user would be an asset for us.

Hello, this would be very interesting for us too

Hello. Any movement on this request? Providing options in more than one language is important to our large user base. thank you