+1 - Need to be able to setup Auto-Assignee and Auto-Watcher via A4J rules.  The global aspect of the team is sorely needed!

I also want to comment on this issue: 

• As the "normal" way to make a field required is also not working for this field, we achieved this with JSU
• Following issue: Within the create linked issue screen, this field doesn't appear. Therefore we can't use this functionality. This is pain in the...

Can you please fix this? 

Best-,

Nicole

Dear all,

I would like to inform you that this issue in the project JPOSERVER is being migrated to the new project JSWSERVER. Your votes and comments will remain unchanged.
Our team at Atlassian will continue to monitor this issue for further updates, so please feel free to share your thoughts or feedback in the comments.

Sincerely,
Aakrity Tibrewal
Jira DC

Time for me to add my two cents.
We have a custom field named Team beyond this System field and because they are both named the same it's causing issues with our Dashboards. Users are selecting the system Team field that is locked. Ultimately it seems we will need to change our custom field and tell all our users to change their setups to use a new field. However this is a really poor implementation of a system field that should either be a very unique name altogether or not locked in our custom fields area.

I cannot even ORDER BY Team...

Jira please at least suggest a workaround.

Looks like this issue was raised 6 years ago but I've recently had to work with the `Team` field and its caused nothing but problems.

Besides whats already been stated in this ticket, these are all the other problems related to the Team field:

• You cannot validate with the JMWE app as the object doesn't act the same as a normal field. This makes it difficult when you want it mandatory via a transition for specific conditions 
• You cannot make Team mandatory because it is locked (extremely inconvenient). I don't understand why a field thats locked cannot be set as mandatory or not considering its optional on an issue regardless of using Advanced Roadmaps
• You cannot have more than 1 team in the field, when we have multiple teams working on a given story/Epic etc

We've had to hack so much to work around the Team field, as we need the Jira portfolio for advanced roadmaps and the hierarchy. The Team field is easily the worst part of the Advanced Roadmap product.
Jira already has a built in users and groups field that works well. I don't understand why they introduced yet another field when they had something like this already. The Teams page under plans is completely basic and almost wants you to do everything manually. For a company that has over 2000 users, how is this a viable solution? We're now having to maintain a custom field that maps to "Team" just so we can get better reporting and queries to work.

Atlassian, please fix the Team field or offer an alternative. As a Jira Admin, I'm getting fed up of having to work around half completed solutions.

I could rant on about the other horrific design flaws in Jira but i'll save that for another day.

In addition to what Nigel wrote in the description, I would add also that it is not possible - or at least we can't find a way - to use the field when integrating Jira to other products out there (Slack, Marker.IO, etc).