Teams was recently introduced natively to automations: https://community.atlassian.com/forums/Jira-articles/Automate-your-workflows-with-Atlassian-Teams-in-automations/ba-p/3187149#U3204912.

This isn't dynamic and doesn't cater for specific workflows. Customers want to be able to use team smart values such as team.teamName or team.teamId.

Some feedback below:

“One piece of feedback: it’d be great if the automation UI exposed team properties (lead, manager, channel) as smart values so we can mention/assign dynamically without hardcoding names. Otherwise, the “Team field changed → move to team board + notify” flow is going to be a huge quality-of-life improvement.”

“Do you have any plans to allow us to add a smart value to populate the Team field dynamically? I just tested the Team field in Automation, and it seems we can only select a team from the Team field (i.e., Set) or copy from other issues (i.e., Copy), but we cannot insert text (e.g., smart value taken from the Asset object).

We have an Asset schema for our teams that also captures extra information such as manager, tech lead, default assignee, capability, various user groups, and a text field containing the Id of the team (manually hard-coded). We use these in a few global automation rules (e.g., set the team based on the assignee or vice versa) or to filter issues based on the user's team membership. In all these automation rules, we use the Additional fields with the team ID stored as text in the team object.

I think the ability to insert smart values is necessary to populate team fields dynamically. We also need JQL or another way (similar to current user conditions within automation) to check team membership dynamically.”

If you are voting for this, please share what smart value you are looking to use and what the use case is i.e. why do you need it and how do you intend to use in your workflows?