Automation issue

[Jesus Octavio Gutierrez Villegas]

Hello everyone, 

First of all, thanks for reading.

I have this issue, this automation is working on other project with different screens, but when i tried to configure this to a new project, is not working... my objective is to copy the value of the native Jira "Team" field, from Parent to Child... this automation is working in another project but here is giving me this error:

Excluded your configured field from this action as it couldn't be found. It may have been deleted, or may need to be added to the project:

Team

Here is my Rule:

[Trudy Claspill · Accepted solution]

Hello @Jesus Octavio Gutierrez Villegas 

Have you added the Team field to the project and to the screens for the issues in the project?

Can you show us the full Audit Log output for the rule execution?

[Jesus Octavio Gutierrez Villegas]

Hello, thanks for your answer.

Yes, the Team field is on both screens, for childs and parent... its present on their Edit Screen.
Here is the full Audit Log:

[Jesus Octavio Gutierrez Villegas]

Team is on these screens:



Parent:




Child:

[Trudy Claspill]

It is possible that there is more than one field named "Team" in your system. 

In your JSON you are trying to update field customfield_10104. Let us make sure that is the correct field ID.

Use the guidance in the following document to output all the field names associated with one of the issues you've shown.

https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/

Search the output for Team. You should find an entry for it that is preceded by its custom field id; i.e. 

"Severity","customfield_10001":"Team","customfield_10002"

[Jesus Octavio Gutierrez Villegas]

Hi @Trudy Claspill 
Thanks for your answer.

I verified and its the correct ID. I even have the same automation for other projects and its working... same field ID and the Team Field is present on the screens as well.

[Trudy Claspill]

I was running through attempting to recreate this rule in my own system and I noticed something I did not notice previously.

Within the branch you have a Condition that the Team field is not empty, and that is actually the step that is failing.

In my environment in the Issue Fields Condition the built-in "Team" field is not available for selection. I think that the "Team" field you have selected in the Condition is not the built-in Team field that has the field type of "Team Picker".

Can you check your Custom Fields list to see if there is more than one field named "Team"?

[Jesus Octavio Gutierrez Villegas]

you were absolutely right! I dont know why the Field Condition is not setting the right field, I changed it to a JQL condition and it worked!

Result:


Thanks a lot!