Impact of the Jira.issue.editable workflow property in automation
Platform Notice: Cloud Only - This article only applies to Atlassian products 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 rules
Automation rules may fail if the work item can't be edited because of this property. You may see the following errors in the rule'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):
Cause
If the jira.issue.editable property is set to false, the automation rule can't bypass this restriction to edit the fields and the rule execution fails.
Solution
Configure the property
Check the current status of the affected work item, and identify if the property is used in that status. If the property is set as false, change its value to true.
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 issue 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?