Issue Summary

• If the Edit Issue action is tasked to set values for 2 fields (for example, Story points and Active Sprint), the audit log doesn’t show an error message when one field succeeds and one field fails.
• If the Edit Issue action is just set to the field that fails, then the error message appears in audit log.

The logging seems to override the error message when there is one field that was successfully edited for the Edit Issue action.

Steps to Reproduce

Copy the steps from JIRAAUTOSERVER-276 to trigger the error “No fields or field values to edit for issues (could be due to some field values not existing in a given project)”
Replicate Board scenario:
1. BoardA filter is ProjectA only. BoardB has its filter set to Project and ProjectB.
2. Create a SprintA in BoardA, and create an issue in it (issueA for example).
3. Open BoardB then start the SprintA from BoardB.

Automation rule:
1. Create an automation rule (global or project specific) with manual trigger
2. Choose Edit Issue action, and select the fields Sprint and Story Points.
3. Choose the Active Sprint (BoardB) for the set value of the Sprint field.
4. Set the Story Points value to a number.
5. Publish changes.
6. Navigate to any issue (that isn’t included in SprintA) then trigger the rule.

Expected Results

Specifically on automation rule logging
Audit log should show the error message “No fields or field values to edit for issues (could be due to some field values not existing in a given project)”

Actual Results

Specifically on automation rule logging:
The audit log shows the automation run as successful even though the Sprint field was not updated.

Workaround

Separate fields into individual Edit Issue actions instead of combining into one Edit Issue action.