-
Suggestion
-
Resolution: Unresolved
-
0
-
14
-
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
Situation
Issue statuses in Basic Search in the Issue Navigator can only be found by the translation of the language pack used by the current user. The same status in the Advanced search (or JQL), can only be found by the original value.
Steps to reproduce
- Set the Default language of JIRA to English
- Set the user language of JIRA to Dutch
- Create a status "Deleted"
- Through the Translate statuses option, add a translation to Dutch "Verwijderd"
- Generate issues in status "Verwijderd"
Expected result
When searching for issues through the Advanced Search in the issue navigator (or other searches using JQL) in status "Verwijderd", the previously generated issues will be found
Actual result
No issues can be found in status "Verwijderd". However issues can be found in status "Deleted
[JRACLOUD-39215] JQL can not use translated values for status
I run into the same problem but with issuetype, where I want to use translated issue type name
Using IPT plugin module (which is the new recommendation from Atlassian for translations instead of than downloading the language pack), we can change the 'Status' field to something else, but then as other users have noted, it is not possible to search using that field translation rather than 'Status'. Is this going to be fixed?
JIRA translation page https://translations.atlassian.com/dashboard/download?lang=en_US#/JIRA/7.3.4
8 months and still no changes with this issue? Does "Don't f... the Customer" really mean "Don't f... the English Speaker Customer" ? If basic functionality like Search does not work for translated custom fields it does not work at all (and it is not a Suggestion, it is a bug)
Hi,
I don't understand why is this moved from bug to suggestion. If the status shown to the user is different from what he sees in the issue, how can he know what he is looking for?
If jira provides the possibility to translate status (and it does), translations should be used everywhere, not canonical values. Right now it seems to be used randomly in the application which makes it utterly unusable.
Disagree with priority. This bug makes Advanced JQL unusable because users don't know what status or custom field they are asking for.
Best Regards
The same happens with Custom Field Translations.
We have found this problem not just in Advanced JQL. The same happens with:
History tab
Workflow Editor
This seems to be a problem in data center as well. (I can't find an open issue in JRASERVER.)