Automation failing on: Could not find your configured field, it may have been deleted?

[Steve Suranie]

Hi

I am trying to create a simple automation that: 

1. On new ticket creation
2. Refetches ticket data
3. Checks if a field has no value
4. Sets a value for that field
5. Sends an email to the initiator

When I test this automation it fails each time with a: 

The field Incident Source is most definitely in the issue type: 

Here's my automation: 

Is there a way to debug this any more than what is being shown? Any help would be appreciated. 

[Steve Suranie]

 e

[Steve Suranie]

Hi Bill

• The rule actor is still the default - Automation for Jira
• It's a company-managed board. 
• The scope is just the project it is on.
• It is a custom field. 
• It is a select list (cascading)
• It appears in both the create and edit views.

[Bill Sheboy]

Hi @Steve Suranie 

Some quick question to help diagnose this...

Who is the rule actor for that rule, set in the details at the top of the rule?  Is it still the default of Automation for Jira?  If that was changed the triggering user may not have access to the field.

What type of project is this rule in: company-managed or team-managed?

What is the scope of the rule: project, multiple-project, or global?

Is that a custom field, or from a marketplace addon?

If it is a custom field the team added, what is the type of that field?

And, is that field on the views for add / edit of issues?

Kind regards,
Bill

[Bill Sheboy]

FYI, please try to stay to one conversation thread.  That will help others reading this thread in the future know if there are multiple solution approaches to try.  Thanks!

You note the field is cascading, yet the screen image seems to indicate something else.  My understanding is the cascading fields can only be edited with JSON in automation rules.

Would you please post an image showing that Edit Issue Fields action?

[Steve Suranie]

Hey Bill

Which screen capture are you referring to (I posted 3).

Here's the custom field page showing it is a cascading select:

and this is the correct board that it displays on: 

[Steve Suranie]

Here's the set up I did in the automation: 

Nothing on the screen indicated it needs JSON to populate the selection. But I'll try that route and see what happens. 

[Bill Sheboy]

That is interesting!

I am trying this with a Free license, and cannot edit a cascading, custom field using an automation rule, edit issue action's drop-down list.  The JSON edit is the only option.