Building Automation rule to update Team field for Issue Type: Story/Task

[michelle.purcell]

I want to create automation for the following:

• Issue Created
• Condition:  Story or Task
• Condition 2:  Created in our project

I want it to look at the parent link to see what the Team is (Using the number identifier for the team) to add it to the Story or Task created

The team field is not available to change so I have to write it in advanced and must admit, writing json is not one of my strengths.  Any guidance or recommendation would be greatly appreciated 

[Jack Brickey · Accepted solution]

Hi @michelle.purcell ,

While I have not attempted to use the Team field in any automation it is my understanding that it is not supported. A quick check of JAC which seem to validate that - https://jira.atlassian.com/browse/AUTO-525 .

[michelle.purcell]

@Jack Brickey thanks for the quick reply.  That is rather unfortunate! Have a great weekend! 

[Kelly Arrey · Accepted solution]

Hi @michelle.purcell We've tried to use the built-in Team field with no success. Instead, we've created a custom single-select field we call "Agile Team".  This supports using the team names in JQL as well as in automation. Usual disclaimers apply: YMMV, deuces are wild, etc.

[Jack Brickey]

Yep that is the best approach until Team matures IMO.

[Kelly Arrey]

As an aside, we've also defined Jira groups with identical names, so you can do JQL queries like:

`"Agile Team" = "A-Team" AND assignee not in membersOf("A-Team")`