Issue Summary

Editing a multi-user-picker field using data from web response or any other means, will show the user as inactive in the audit logs, even when the user is active. This is seems more of incorrect logging as user is added successfully.

Steps to Reproduce

1. Create an automation rule
2. Add a "Send web request" action where the user's email address or accountId (i.e user search API) can be returned by the web request call and ensure the account in question is active under User management.
3. Add an "Edit issue" action, and edit a multi-user-picker field, then add the following smart value:

   1. {{webresponse.body.first.accountId}} 

Expected Results

The log shows that the field was edited without a warning that the user is inactive.

Actual Results

The log shows that the field was successfully edited, but warns the user is inactive even when is not. User is added to the multi-user picker field.

Workaround

Scenario: You're using JSM Assets Attribute to pick up the user details and trying to update a multi-user picker field, which causes this error.

Workaround: Use 'Create Variable' action to capture the Attribute Value in a variable, and use the variable to update the field. This works in some cases.

Workaround 2: Use a JSON to update the field.