Description
Today, users can be assigned to multiple teams in the native Jira Team field. While this works well for collaboration scenarios, it creates challenges for automation use cases where a single team must be determined automatically.

We request the ability to define one team as a user's Primary Team (or Default Team). This designation should be accessible through Jira Automation and related APIs.

Use Case

A user belongs to multiple teams:

• Team A
• Team B
• Team C

The user manually triggers a Jira Automation rule that creates work items on their behalf.

The automation needs to determine which team should be assigned to the created issues. Currently, there is no native way to identify a default team when multiple team memberships exist.

With this enhancement:

1. Administrators can mark one team as the user's Primary Team.
2. Jira Automation can access the Primary Team through a smart value.
3. The automation automatically uses the Primary Team when assigning fields, routing requests, creating tasks, or populating team-related metadata.
4. If a user belongs to only one team, that team is automatically treated as the Primary Team without additional configuration.

Example

User: John Doe

Teams:

• Operations
• Platform Engineering
• Enterprise Architecture (Primary Team)

Automation:

• User triggers an automation rule.
• The rule creates one or more issues.
• The Team field is automatically populated with Enterprise Architecture because it is configured as the user's Primary Team.

 
Business Value

1. Simplifies automation design and eliminates complex workarounds.
2. Reduces incorrect team assignments.
3. Improves consistency across issue creation, approvals, requests, and asset workflows.
4. Enables scalable enterprise use cases where users often belong to multiple teams.
5. Reduces administrative overhead and custom scripting requirements.

Expected Behavior

• A user can have zero or one Primary Team.
• The Primary Team can be configured in the user profile or Team administration.
• Jira Automation, REST APIs, and Forge apps can access the Primary Team.
• Existing functionality remains unchanged for users with a single team membership.

Additional Context

This feature is particularly valuable for enterprise environments where users commonly participate in multiple teams but require a single default team for automation, workflow routing, reporting, and ownership assignment scenarios.