Jira automation is not recognizing a custom field

[Christy Kennedy]

I have an automation that is trying to create different subtasks on an issue depending on the values of 2 custom fields: Region & Entity.

I keep getting an error in the audit log that says the field "Entity" has been excluded from my if/else block as it couldn't be found.

I tried forming the if/else conditions using JQL with "Entity"'s custom field ID, but I got the same error message.

I have also confirmed that this field is configured for use in my project.

[John Funk · Accepted solution]

Hi Christy,

Make sure the Entity field is on the Create screen for the Project and Issue type. 

[Christy Kennedy]

Hi John - yes, it is on the create screen

[John Funk]

So, if you click on the Create button, and you put in that project and the Approval issue type, you see the Entity field on that screen?

[Christy Kennedy]

Correct - it is even a required field

[John Funk]

Ah! So maybe there is not a value for that field. Can you share the details of how you are populating that field in the rule? 

[Christy Kennedy]

Aha! I did not realize that the error message meant 'Entity' was not being populated in the subtask the automation is created, I thought it was not being analyzed as part of my if/else conditions.

The problem is actually that it isn't copying the value of 'Entity' from the parent ticket:

[Christy Kennedy]

Thank you @John Funk!

[Christy Kennedy]

How I fixed for reference:

The circled 'Entity' field above is actually an old custom field with the same name that has been deleted. I needed to remove it from "Choose fields to set", then add the correct "Entity" field that is included in my issue type's screens

[John Funk]

Awesome! Glad you got to the bottom of it and got it fixed. 

[Bill Sheboy]

Hi @Christy Kennedy 

Here are some questions that may help explain this symptom...

1) What type of project are you using: company-managed or team-managed?  You may find this information in the project list.

2) Did you add the custom field Entity or was it added by a marketplace addon / app?

3) If you added the custom field and you are using a team-managed project, where was it added: to the global fields (i.e., company-managed) or in the project's fields in the team-managed project?

4) Are there multiple fields named Entity within your Jira site, either global and project, or for multiple, team-managed projects?

5) For the trigger issue's issue type, have you confirmed that field is available?

6) What is the scope of this rule (in the details at the top): single-project, multiple-project, or global?

7) Rather than using the Issue Fields Condition, have you tried using the Smart Values Condition and the custom field ID to test the value?

Kind regards,
Bill

[Stephen_Lugton]

If you don't know how to find the custom field ID @Bill Sheboy mentioned have a look here: https://confluence.atlassian.com/jirakb/how-to-find-id-for-custom-field-s-744522503.html

[Christy Kennedy]

Hi Bill,

1) Company-managed

2) I created the custom field Entity

3) n/a - company-managed project

4) There is only one field named "Entity" as far as I can tell by checking global Custom Fields & doing a JQL search. Not familiar with how to check other team-managed projects though

5) Yes, the issue type in the trigger is "Approval" and Entity is available in  all screens for "Approval" type issues

6) Scope is single project - and it is the one I am testing this rule on + the only project that uses the issue type "Approval"

7) I have not tried using the smart value for my if conditions - trying that now and will update shortly!

[Christy Kennedy]

Update on using a Smart Value with the custom ID field:

Still receiving the same error:


Updated rule logic: