+1

We at Amnesty International Germany are introducing Jira Service Management and have to provide two languages (English and German). The field "Customer Request Type" was first setted up in German: "Kundenanfragetyp". Now our english speaking employees all are wandering what the hell "Kundenanfragetyp" means. And I got no chance to translate this - it is a locked custom field

+1

+1

+1

So much years to fix an issue that should be really easy to fix judging by the workaround  but probably never gonna be addressed because the workaround is too simple.

I guess for Atlassian, people who don't speak english exclusively should wait at the end of the line this workaround is like adding duct tape on leaky pipes

There are so many issues like this one in "gathering interest" state, it would definitely make sense to merge them into a single one as they all have the same intention. If voting is spread across so many issues, none of them will likely reach a relevant interest ever.

Not being able to translate fields that are functionally mandatory makes the user interface pretty unattractive and hard to use.

Very important ... this is a blocker for us, as having mixed language UI's is borderline illegal for us. I could end up having to hide all the locked fields and not use them This is a problem of couse since some are rather important, like the SLAs.

+1

+1

+1