It doesn’t make sense for us, as users, to have to find a workaround when your team is so close to providing a fix. All the forms have already been translated—please just finalize this last part. Thanks!

Please, we need this features as fast as possible...

When would this be available!?! Amazing that is not still available...

It's a shame, quite embarrassing really, that an issue like this sits there untouched for over TEN YEARS, and that people STILL have to beg for the implementation.

Come on Atlassian!

This request has been open since 2014, yet no progress has been made! While Jira manages most aspects of translation effectively, there is a persistent issue where a multi-choice field in a JSM form, linked to custom field options in Jira, cannot be translated at all.
790 votes are not enough to have this issue taken into account!
I understand that this issue may not be simple to resolve, but could you please provide a workaround or at least an explanation?

Hi 98d8117ed7d4 is this item still "Not Being Considered" ?

Is it so difficult for Atlassian to understand that there are companies that work in more than one language? What use is a supposedly multilingual interface if the options cannot be translated? We work across several language areas (FR/EN/JP/CN/PT/ES/EN/DE). As a Westerner, just try using a Japanese GUI with Japanese option fields! Do the test! Then you might understand the added value for the product a little faster. 
(Poor work by the product owner. This is NOT multi-language what you currently offer. It is only half-finished work)

One would think, that after yet another huge increate in Licensing fees, that there should be enough money left to implement a 10 year old request, that is so fundamentally important. 

@Atlassian - sometimes I do wonder, how your decision process works.

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 using 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.

Yes I need this!!! We need this!

I shouldn't have to vote for this; it should be a basic feature! Why can I translate custom field details if I can't translate their options? I don't understand.

@Atlassian
Any news on the progress of this one? We can't update all existing request types into forms!
BR Toby

Workaround Solution: 

If it is suitable for you can use forms translation feature with JSM portals.

https://community.atlassian.com/t5/Jira-Service-Management-articles/New-Multilingual-support-for-Forms-in-Jira-Service-Management/ba-p/2751427

Please can someone figure out how to incorporate AI into this issue, so it might actually be put on the roadmap?

It's been 10 years... please, it shouldn't be possible to offer a multi-language platform without the ability to translate the options for custom fields.

The ticket has 766 votes, what else is needed to prioritize this item?

We have implemented a workaround by using forms fields and provide the translations via translated forms field values. 

Then we have a scriptrunner script which automatically copy the forms data into the description field for better sharing the form with other projects

we need it

Please almighty Atlassian, we beg of you! This would be an awesome and incredible boost for us

Thank you for prioritizing this request

Wishing you a great day

Still waiting for this 

In a country with 4 national languages this is important to have.

That request is now 10 years old. Someone seems to be a slow thinker.

What's the point of translations if the most important part of the information (Select values) can not be translated?

This is a must have I would say.

Happy birthday to this request!  10 years!

This would be extremely helpful to our global organization.

This is a must have for any international company, like my own and apparently many others. Let's do this!

Edit: I want this for every single word that a user can see. One should be able to translate everything.

Any news on the progress of this one?
BR Toby

What's up about this issue ? 

It's very important for our internationnal client to translate custom field options for List , radio button and Checkbox.

We're waiting any news on this topic ! 

Hey Atlassian:

What are you waiting for?

You have a great product, but this feature is very important for some of our customers. One of our customers refused to switch from XXXX to Jira for this reason.

By the way here is a new app

https://marketplace.atlassian.com/apps/1234677/translated-fields-for-jira-jsm?hosting=cloud&tab=overview

We receive complaints about the unprofessional appearance of our Jira Service Desk because we provide request types with information in several languages. When we then explain that the software doesn't allow us to change this, we get raised eyebrows. Atlassian should really come up with a solution to avoid negative effects on the overall image...

This is really crutial to provide proper UI/UX for our customers on customer portal. I am so surprise that this is not nativelly supported.

i do hope this gets implementated sooner rather than later. Not having the translations & agents using JSM in their own language, get transistions in English, and not knowing for certain what they are. Please Atlassian, implement this now, to bring JSM to the next level.

This would alleviate one of the biggest pain of those working with JSM in a multi-language environment.

There are some features that should not be considered "Under Consideration".

You should transition to "In Progress"  

A must have to be able to deploy your solution in a multi-language company. A real blocking point to go forward with altlassian product.

+1

Hi we would love to be able to fully translate these custom field contexts very interested in this development!

Agreed. This would be a great addition to solidify Jira's commitment to large-scale international organizations.

This is really important. JSM is so popular now and companies really international. Hopefully this will be implemented soon.

Any updates?

Essentially for users which use other than the English language pack

Any news on this? It does not make sense you are able to translate the fields on your request types but not the options, that's like only half a solution.

Definitely a critical feature in our international organization. One of the reasons our IT team is currently evaluating ServiceNow, which can publish KB articles in multiple languages.

Merry Christmas to everyone and I wish us all that Atlassian has many New Year's resolutions - e.g. to solve this issue!

How Jira SD is supposed to work with global customer base if option translation is not available?
It's must have for multi-national service organization. 

Adding my voice to the request to provide support for translation of customer field options.
Lack of full support for translation is making me consider moving away from JSM.

I am not ruing the cloud version bu the data center version.  I need to upgrade.  It has always said in-product translations is unknown but it just worked.  It is written by atlassian.  I am not in a clustered architecture.   I just upgraded from 8.20.13 to 9.4.10 the menu option was still there under add ons but the translations were missing.    Are there lower version for 9.4 that may still work??  The instance relies on it heavily for all its menu items.

This is essential for us as well. It's quite surprising that Atlassian missed this aspect. I'm looking forward to seeing this feature become available in the near future.

Just my reminder on regular basis, that this is a crucial feature. Any bets how long it will take? 

I go for minimum 2 years from now on.

Any update?
We want dropdown fields to be translated into specific language 

I can no longer find the link, but I took part in an "Ask Me Anything" session where Atlassian mentioned that translations are coming for Forms. Personally, I hope that all options will be translatable; otherwise, the feature is half-baked.

On the server version the translation was possible.
Why this was not transferred to the cloud is a step backwards on the part of Atlassian and also for our customers with the selection fields not being able to display the translation.

Surely all here who leave a comment on this agree with me that this must be solved as soon as possible.

In what time frame does Atlassian have a solution here?
For what reason was this not adopted or considered in the cloud?

We use options in custom fields in JSM. We miss the feature to translate the options of the custom fields.

any news?

It should be support with Jira Service Management portal.

I can totally agree with everyone commenting here, it just doesn't look professional if you can't translate the language of the options. Please provide us with further information regarding the solving of this issue!!

I'm worried as this is unassigned, I hope someone see the new comments.

Our business concern is with the "Language Support" feature of JSM, where not being able to just translate options from selection fields (lists, checkbox, etc) on the customer request form gives a bad requester experience.

In our case, it doesn't have to be a full instance wide translation for custom fields options; just being able to translate these options using JSM Language support UI would  be enough. On Cloud, there isn't a marketplace app known to us that address this.

Renaming options on all fields on an existing live Jira installation is too effort-heavy to be a viable workaround, with all the colleteral impacts of renaming them.

do you have any news for us? When will it be ready for release?
BR Toby

+1