Impact of the Jira.issue.editable workflow property in automation
Platform Notice: Cloud Only - This article only applies to Atlassian apps on the cloud platform.
Summary
The jira.issue.editable workflow property key controls whether a work item can be edited on a specific status.
For example, once a work item is in a “Done” status, you may want to restrict editing to ensure no data changes after it is completed.
Diagnosis
Impact of jira.issue.editable on Automation Flow
The Automation flow may fail if the work item can't be edited due to this property. You may see the following errors in the flow's audit log:
Edited work item successfully, however some of the set fields aren't available. Fields ignored:No fields or field values to edit for work items (could be due to some field values not existing in a given project):If you see either of these messages and the fields you expected to change weren't updated, check whether jira.issue.editable is set to false on the work item's current status. See Cause for details.
Cause
If the jira.issue.editable property is set to false, the Automation flow can't bypass this restriction to edit the fields and the flow execution fails.
Solution
Configure the property
This property is set per status, confirm the work item's current status before changing the value — a status that permits editing elsewhere in the workflow may still have jira.issue.editable set to false
Use case | Key | Value |
To make a work item editable when it's on a particular status. | jira.issue.editable | true |
To disable editing when an work item is on a particular status. Often used on final status. | jira.issue.editable | false |
You can read about this and other workflow properties at Use workflow properties.
Was this helpful?