Request Type Update Fails in Automation
Platform Notice: Cloud - This article applies to Atlassian products on the cloud platform.
要約
The automation rule fails to edit the "Request Type" field with the following error:
Edit request type
Error in updating the request type
Field 'customfield_xxxxx' cannot be set. It is not on the appropriate screen, or unknown. (customfield_xxxxx)
診断
Generally, this issue happens if the "Request Type" field is not added to the "Edit screen" of the Issue type. However, this error is also caused if there are 2 "Request type" fields with the same configuration found in the Custom fields.
原因
The 2 "Request type" fields found are:
- The main field "Request Type" is the one that the automation rule should have updated but it is referring to the other one.
- The "Request type" is the one with the description: "Request type created by JIM during import process". This field is created during Migration/Import.
Usually, the backend uses the main request type created by the Jira Service Management but on the UI, the system tries to set a different field.
ソリューション
To fix this concern, you need to Delete the "Request type" field created by JIM during the import process permanently. To delete the field, refer to the below steps:
- Select Settings > Issues.
- Under FIELDS, select Custom fields.
- Search for the field "Request type" created during the import process >>click on More (three dots) > select Move to Trash
- Now select the "Trashed" tab from the top and select Actions (…) > Permanently delete.
Permanently deleting a custom field also deletes all the data stored against that field. You can’t undo this. If you want to keep field data for historical records, we recommend you back up your Jira site before permanently deleting fields. Learn more about backing up your Jira site.
Lastly, go to your Jira Automation Rule, delete the edit request type action, add it again, configure it, and publish the changes.