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" ?

Happy New Year, everyone! May it be filled with joy, success, and - who knows - maybe even some miracles. Like Atlassian resolving to fix this bug. We can dream, right?

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.