The assignee field in Jira allocates tickets to a specific user. However, sometimes the person assigning tickets isn't all that familiar with the users they're assigning tickets to: they don't know their expertise, when they're on annual leave, or their overall workload.
Teams versus Groups
It would be better to assign tickets to many people, and someone closer to that team can decide how these are allocated. This can be done using Jira Groups or the Team field, but which is best?
The Team field can be set up by anyone, and members can be assigned to alerts, components, and services. These can also be used in plans and advanced roadmaps.
Groups are set up by admins, and can be used in project roles and permissions, workflows, automation rules, filters and dashboards, product access, and other Atlassian products. You can apply contexts and default values in the Group Selector fields, and they work with JQL, notably the membersOf() function. Group members can also be synced with an identity provider like AAD and OKTA for group management.
Teams AND Groups
Rather than choosing between the Team field and Groups, what if you could combine the power of both, while keeping members in sync?
We've written a tutorial with example scripts showing you how to do this ScriptRunner.
