-
Bug
-
Resolution: Duplicate
-
Medium
-
8
-
Severity 3 - Minor
-
3
-
Issue Summary
Custom Priorities breaks SLA configuration when user profile language is changed
Steps to Reproduce
- Set your profile language to English (UK/US)
- Create a custom priorities, lets call it 'Critical'
- Now setup a SLA goals with 'Critical' priority and simple JQL something like "project = <project_name>" then save the configuration
- Change your profile language to non English like Spanish/Portugal/Polish
- Navigate back to SLA configuration page within your project, click Edit goals.
Expected Results
SLA configuration should be displayed correctly
Actual Results
You get an error message in two different places:
- At JQL filter- which translates to "This SLA has one or more errors."
- At Priority column - Which translates to "This priority no longer exists. Check your Jira priorities or delete this time goal."
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- is related to
-
JSDCLOUD-13560 Setting up SLAs per priority will not work properly when different languages are involved
-
- Closed
-