-
Bug
-
Resolution: Fixed
-
High
-
None
-
17
-
Severity 3 - Minor
-
2
-
Steps to Reproduce
Automation Rule:
- Create a new Automation on a Service Desk project;
- Select the Issue Created trigger;
- Add an Edit Issue action, and select the Assignee field;
- Select a user, click add and save the automation;
- Open the automation again and click the pencil icon to edit the action;
Request Type:
- Add the assignee field to a request type and hide it;
- Select a user, click on "Set";
- Edit the value again;
Expected Results
The selected user is displayed as the chosen assignee.
Actual Results
The assignee is displayed as "Automatic".
Notes
The user is actually stored properly, it's just not being displayed properly. If you try selecting the same user again, the option to save the automation will be grayed out as no actual changes were made.
Workaround
Currently, there is no known workaround for this behavior, but please note that the actual value is being stored. A workaround will be added here when available.
- is related to
-
JSDCLOUD-8500 Hidden user picker fields missing values on request types
-
- Closed
-
-
JSDCLOUD-8583 Renamed users cannot be selected as preset user in Request Type configuration
-
- Closed
-
-
JSDCLOUD-8619 User cannot be added as default approver on customer portal request for specific users
-
- Closed
-
- relates to
-
JSDCLOUD-8601 When user_key and lower_user_name do not match, user can not be added as Assignee
-
- Closed
-