What are the current use cases of the "Teams" field in Jira Cloud?

[Sami Shaik]

Hello Guys ,

I’ve recently noticed the Teams field available in Jira Cloud and wanted to get clarity on its practical usage:

• Where exactly does the Teams field help today (e.g., in reporting, issue tracking, or planning)?

• Can we use Automation for Jira to update or manage this field?

• How is the Teams field leveraged in Advanced Roadmaps/Plans and Atlassian Rovo?

I’d love to hear how others are making the most of this field and whether it’s worth adopting in day-to-day Jira project management.

Thanks in advance for your insights!

[Jack Brickey · Accepted solution]

Hi @Sami Shaik , here are some of my use cases.

• used to group and identify team ownership of issues
• used to create/define Boards in CMP projects 

you can use Teams in Automation but will need to use JSON to reference using the custom field ID, e.g. customfield_21829. It is certainly integrated in Advanced roadmaps to group issues by team. I have not use with Rovo but I am quite sure Rovo can leverage, e.g. "find all issues resolved last week by the xxxx team"

[Chitra Nagdeo]

Hey @Sami Shaik ,

Welcome to Atlassian community! I understand you are looking for details related to Teams field in Jira, refer necessary articles here. I will try to answer individual queries below:

a. Reporting & Issue Tracking

• The Teams field is designed to standardize how teams are assigned to issues, replacing the need for custom “team” fields across projects.

• It enables filtering and grouping issues by team, which is especially useful for large organizations managing work across multiple teams.

• However, there are current limitations: for example, the Teams field cannot be used as an axis in two-dimensional dashboard gadgets, which restricts some reporting capabilities.

• Inconsistent use (e.g., not making the field mandatory) can lead to poor data hygiene and less effective reporting.

• In the issue view, the Teams field can be surfaced and used to replace custom fields, streamlining team assignment and improving data consistency.

b. Planning (Advanced Roadmaps/Plans)

• In Advanced Roadmaps, the Teams field is central for capacity planning, scenario modeling, and visualizing work by team.

• Teams can be set up as shared (across plans) or private (plan-specific), and you can assign issues to teams, set team velocity/capacity, and group/filter work by team.

• This enables program managers and team leads to allocate work, monitor progress, and manage dependencies at the team level.

• Team assignments in Advanced Roadmaps are used for forecasting, reporting, and aligning work with organizational goals.

c. Automation for Jira to update or manage the Teams field?

• Company-managed projects: You can use Automation for Jira to set or update the Teams field using the “Edit issue” action, as it is a standard custom field in these projects. Refer FR: Support for Teams field in Automation, e.g. Company-Managed Projects and Ability to Use Team field in Issue condition Field in Automation for jira

• Team-managed projects: There are limitations—automation rules currently do not support all custom fields, especially People fields, in team-managed projects.

• For advanced use cases, you may need to use the “Advanced fields” (JSON) option in automation to update the Teams field, but this depends on your project type and field configuration.

• Article to get the JSON syntax for Teams field 

  Automation: Update the Team field based on the Assignee field

I hope the above explains the usage of field and its existing limitations. Have a good day!

Regards
Chitra Nagdeo