Issue Summary

Edit Issue action is unable to edit fields e.g. DueDate on an issue if the rule actor does not have permissions to edit the issue.

Steps to Reproduce

Create an automation rule to edit fields and ensure that the actor of the rule doesnot have edit issue permissions in the project.

Expected Results

The edit issue action shhould fail with an error such as "Actor doesnot have permission" .... or something similar depicting a permission or access issue. 

Actual Results

Currently if the Actor, doesnot have a valid JSM license, is not added to the project as an agent or doesnot have edit issue permissions the below errors are seen: 

Error 
Edited issue successfully, however some of the set fields aren't available. Fields ignored:

Actual end (customfield_1xxxx)
Unable to find any issue field values to edit:

ABC-123 

This creates a misunderstanding about the error related to field configuration, instead of user permission.

Workaround

Provide the required license, agent roles, edit permission to the Actor of the rule. 

or

Change the actor of the rule to a user who has these permissions.

Update

Workflow properties might also lead into the error if the property prevents issue editing. A suggestion in this case is to add a property granting the permission to the role atlassian-addons-project-access like in the example below:

• Property Key: jira.permission.edit.projectrole.1
• Property Value: <ROLE_ID>

The ID of the role can be retrieved by hovering over View Usage in the global project roles page: https://<SITE>.atlassian.net/secure/project/ViewProjectRoles.jspa