Details
-
Bug
-
Resolution: Timed out
-
Low
-
1
-
Severity 3 - Minor
-
0
-
Description
Issue Summary
If the user's locale is different from the tenant's default locale then Jira will attempt to translate multiple strings in the system, such as priority and issue type names and descriptions, even if those values have been changed (i.e. different from the default).
Steps to Reproduce
- Set a user with a different locale compared to the one that is used in Jira by default. For example, if Jira default locale is set to en_US locale, change the language in user's account preferences to English (UK).
- Create a priority called "critical", note that all letters are small
- Use the API to get the priorities from Jira: https://<instance name>.atlassian.net/rest/api/3/priority
Expected Results
The name of priority in API response is the same as it is visible in Jira database and on UI https://<instance name>.atlassian.net/secure/admin/ViewPriorities.jspa
"self":"https://<instance name>.atlassian.net/rest/api/3/priority/<priority id>", "statusColor":"#000000", "description":"Atlassian test", "iconUrl":"https://<instance name>.atlassian.net/images/icons/priorities/blocker.svg", "name":"critical", "id":"<priority id>"
Actual Results
If the user locale is different than Jira default, "critical" priority is fetched by API as:
"self": "https://<instance name>.atlassian.net/rest/api/3/priority/<priority id>", "statusColor": "#000000", "description": "Crashes, loss of data, severe memory leak.", "iconUrl": "https://<instance name>.atlassian.net/images/icons/priorities/blocker.svg", "name": "Critical", "id": "<priority id>"
Workaround
Set users's locale to match Jira default locale.