We would welcome the implementation as well. It's annoying that I have to explain my users what they need to enter for status, resolution and field names in JQL. Sometimes the german term (user defined) sometimes the english term (JIRA standard).

Your statement that we could edit the resolution is not so good. Then all existing filter were broken, right?! Also, that does not work for status and field names (priority, assignee, reporter). And as an admin you can't change the filter for the users ( ).

In your example of Resolutions, you currently have a "real" value of "Duplicate" and then have added a German translation over the top of that.
If all your users are German, then you can edit that Resolution to have "Duplikat" as its primary name, but of course this is unsatisfactory if you have mixed users.

This is a bit tricky.

Because JQL can be saved and shared to be run by other people, we need to make sure it is stored in an unambiguous (Locale-free) format.
This means that neither the field names nor the field values are translated in JQL ... they all use the "primary" value because it is unambiguous.

If we wanted to solve it we would have to convert the locale-specific "displayed" JQL to an unambiguous storage format in order to run it, and then also convert this storage format into a locale-specific display version in order to show saved filters ... with all sorts of messiness like that resolutions primary values are guaranteed unique but translations are not.