Automation fails to update Actual End date when jira.issue.editable is set to false

Question

I'm try to lock all the fields when the status of the CR is transitioned to CLOSED.

I'm using Automation rule to update the Actual End date, but it fails with the below details.

Unknown fields set during edit; they may be unavailable for the project/type. Check your custom field configuration. Fields ignored -Actual end (customfield_13547)No fields or field values to edit for issues (could be due to some field values not existing in a given project):I check all the fields configuration, and everything looks right. Can u help me

Dinesh Balakrishnan · Answer

Can u help me with the "cannot edit in this status" workflow property, that can be used as an exemption.

Nic Brough -Adaptavist- · Answer

I thought this was the case.

Your automation is trying to edit an uneditable issue.  Automations happen after transitions, so your Automation is trying to update an issue in "completed (and hence un-editable)" state.

You either need to provide an exemption to the "cannot edit in this status" workflow property, or move the automation into a post-function so that it updates the data during the transition, before the issue becomes uneditable.

Dinesh Balakrishnan · Answer

Step 1 : Transitioning from "Awaiting implementation" to Implementing ->

Actual Start gets update to now() by the Jira Automation. jira.issue.editable is not set here. All good here. Actual Start (Has a value)  & Actual End (null) visible on the Issue screen.

Step 2 : Transitioning from "Implementing " to Completed ->

Note : jira.issue.editable is set to false. Automation is in place to update the Actual End date.

Actual Start has a value and Actual End date disappears from the Issue Screen. While checking the Audit log, I found the above error.