-
Type:
Bug
-
Resolution: Duplicate
-
Priority:
Low
-
Component/s: Automation - Action - Edit request type
-
None
-
Severity 3 - Minor
(JSM) When a customer with the default language selected as anything other than English creates a request from the portal, the Automation rule is not able to Edit Request Type.
Issue Summary
(JSM) When a customer with the default language selected as anything other than English creates a request from the portal, the Automation rule is not able to Edit Request Type and performs no action.
It looks near to https://jira.atlassian.com/browse/JSDCLOUD-15087
JSDCLOUD-15087uses "If:add a condition" rule.- This ticket uses Action: "Edit request type" rule.
Steps to Reproduce
- Configure Request Types of a project with the language set to English.
- Add Language support "not English" like Dutch, Japanese.
- Add Translate the name of the Request Type.
- Change preference language to added language.
- Create an Automation rule with the Action: "Edit request type" in which the above Request Type is selected. You can select "translaged" request type.
- Run Automation.
Expected Results
The Automation rule work successfully
Actual Results
The Automation rule will fail with following error.
The chosen request type doesn't exist in this issue's project. Check if the request type has been deleted from the project.
Workaround
Before setting Automation, change user account preference language to English. set Automation.
- relates to
-
JSDCLOUD-15087 (JSM) When a customer with the default language selected as anything other than English creates a request from the portal, the Automation rule is not able to translate Request Type and performs no action.
-
- Closed
-