Summary

Learn how to resolve the "Could not find your configured field, it may have been deleted, or may need to be added to the project" error in automation rules for edit work items actions.

Identifying the problem

• Check if the field added to the edit work item action in the automation rule is also added to the work type screen. 
  • This can be verified by going to Project settings > Screens.
• If the field is added in the associated work type screen, then on a particular issue view, find the field. 
  

  • Select ··· > Find your field.

  • Search for the field you want to find.

  • Select the field.

  • Check if there are any errors.

Field not added to the project scope

There can be multiple reasons for this error to occur, and one of them is that the affected field is not configured in the scope of the Project and work type.

To rectify the errors, follow the steps below: 

1. Navigate to Cogwheel > Work items > Custom fields. 
2. Search for the affected field, then click on ••• > context and default values.
3. If the project or work type is not added in the context of the custom field, then add the project or the associated work type to the context.
4. Select > Work items.
5. Under FIELDS, select Custom fields.
   1. Find the custom field you want to configure and select  > Contexts and default value > Add new context. 
   2. Enter a label and description for your new context. These are used for your reference in the administration section only and will not be shown to your end-users.
   3. In the applicable work types section, select the work types that you want this custom field to appear in. 
   4. In the applicable contexts section, select a global context or choose specific projects that you want this custom field to appear in. Note that the custom field will only appear on work types you previously selected.  
   5. Select Add
6. Additionally, check the default configuration scheme of the custom field. 
7. Add project or associated work type to the context (Follow the same steps mentioned as above).

Reference:

• Configure custom field context