Issue Summary

While having a Custom Field that's not present in a Jira Screen, and using an Automation to set this Custom Field's value, the message below is thrown in the Automation's Audit Log:

"Edited work item successfully, however some of the set fields aren't available. Fields ignored"

This seems to only happen when the Rule's Actor is User who triggered this event; And it might be related to what the User sees in the Screen.

However, when changing the Rule's Actor to Automation for Jira, no warning/error messages are displayed in the Audit Log - and more importantly, the field value is successfully set.

Steps to Reproduce

1. Create a simple Automation Rule to set a value to a Jira Work Item Custom Field
2. Make sure the Automation for Jira actor is set to this Rule
3. Create a new Work Item, and make sure the Field is not present on its Screen
4. Run the Rule against the Work Item, setting any value to this Custom Field
5. The Field's value is set, it's possible to check the Audit Log and no errors are present
6. Now, in the Rule's configuration, change the actor to User who triggered this event
7. Run the Rule against the Work Item, setting any value to this Custom Field
8. The message above is displayed in the Audit Log entry, and the field value wasn't set

Expected Results

One of the two:

• Give more details why the value being set has failed, and update the documentation regarding it explicitly
• Preferably, set the field value as expected while running the Automation Rule

Actual Results

An Audit Log message informing the Fields aren't available.

Workaround

For now, changing the Rule's Actor to Automation for Jira.