Community
Q&A
Jira
Questions
New syntax for setting the Team field in an automation?

New syntax for setting the Team field in an automation?

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?

2 answers

2 accepted

1 vote

Answer accepted

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 🤠

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Thanks @Arkadiusz Wroblewski ! I found that using "customfield_10001" as documented in your second link worked!

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Like • Arkadiusz Wroblewski likes this

Glad to hear that 🤠 ☀️

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

1 vote

Answer accepted

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

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

I don't think Team is a custom field. I do not have admin access to add a field. Is there another way to find out the custom ID?

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

NM... found it in one of the links below: "customfield_10001"

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Like • Arkadiusz Wroblewski likes this

you can set my response as accepted it's free ;)

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Forums

Q&A

Community resources

Support

Top groups

Community resources

Support

Learn

Community resources

Support

Events

Community resources

Support

New syntax for setting the Team field in an automation?

2 answers

2 accepted

Suggest an answer

Was this helpful?

Thanks!

DEPLOYMENT TYPE

PRODUCT PLAN

TAGS

Community showcase

Atlassian Community Events