New syntax for setting the Team field in an automation?

[Michelle_Benes]

Copying the Team in my automations stopped working around 1:30 ET today...

I have two automations that use the following code in the “Additional Fields” section.

"team": "{{triggerIssue.fields.team}}"

This worked until today, but now I’m getting errors. I tried setting the Team field above (instead of in the additional fields), but when I search for “Team” it only shows the first 50  fields with the team in the name, so I can’t select it. (Our Jira instance has way too many custom fields!)

The error in the log is:

Additional fields contains invalid field(s) in 'update' or 'fields' section. team

Does anyone know if the syntax for this has changed?

[Ignacio Vera]

Have you. tried replacing "team" with the actual custom field ID? Search Team in Fields and check if you get a custom field id when you hover on Add field to screen.

Then use that field ID on your automation

[Arkadiusz Wroblewski]

Hello @Michelle_Benes 

I don’t think this is a new syntax, Automation is started being stricter about the field key.

The Team field is a custom field in Jira Cloud. Using `"team"` in Additional fields is mostly unreliable. More stable is to use the actual `customfield_xxxxx` ID and pass the Team ID/UUID as the value.

Change is probably that the old `team` shortcut/alias is no longer accepted by the automation validator.

Here some official KB Articles related to That. 

https://support.atlassian.com/platform-experiences/docs/using-atlassian-teams-in-jira-projects/

https://developer.atlassian.com/platform/teams/components/team-field-in-jira-rest-api/ 

Best,

Arkadiusz 🤠