Please, please. We were fine with the clunky JSON method that never worked exactly right, but now that we are using the Goals feature on Atlas (or Platform Experiences), which relies on the Team field, this takes on a new importance. Please help make this a fully production-ready feature. 

The current work around of using the JSON advance edit is ok but it doesn't fix all the issue with team field like notifications and being able to @ the team in comments. Typically, only able to assign a team to a work-item. When the Team field was being created to support the idea of teams in Jira it was missing some key abilities when released. We need it to do more to connect the idea of teams across the system of work. Automation, notifications, identity, permissions, etc. 

+1, need to inherit team field from parent to create the project roadmap

+1 please fix, very weird that we need to create a proxy field for this. So many people ask questions about this. 

Hello,

My organization relies heavily on the Team field. All our agile boards are built on filters using Team, for example. It would be incredibly helpful for us to set this field in our various automations without clunky workarounds that require support tickets, a lot of trial-and-error testing, and that sometimes don't even work. It's been surprising since our move to Jira that Team is not a first-class field.

I'm currently working with Atlassian support to fix a couple automations, and it's taking a lot of time! If this was supported it would have been a 20 minute task rather than one that's spanned multiple weeks.

https://codebarrel.atlassian.net/browse/ACF-15105

Hey all, 

I've tried to use the workaround proposed here https://jira.atlassian.com/browse/AUTO-525?focusedId=3340288&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-3340288 

The error is 
Additional fields contains invalid field(s) in 'update' or 'fields' section: Team
but the automation rule can't be saved at all. Any suggestions?

P.S. Voting on this!

We are using the new teams, but I'm still struggling using this in automation. Is this correct? 

{
 "update": {
    "Customfield_10001": 
   [
         

    ]
}

@Jeremy, if you have only a 5-digit id, your instance has maybe not yet rolled-out on the new Team concept, and you are still using ex-AdvancedRoadmaps Shared teams. But yes, you can use it in Automation

Your id will probably be migrated when rolling-out, but be aware of this change https://www.atlassian.com/wac/roadmap/cloud/unification-of-our-team-concepts?p=3e20b18b-bc , and you will have Teams with a longer id

@Florent or @Jamie, how do I edit a shared team I created to get that king of team id in Jira Cloud? All I can find is a 5 digit numerical when searching for the team in a simple issue search and that number doesn't seem to work in my automation rule.

Resolved with the 5 digit id.