Issue Summary

A customer has requested an enhancement to Advanced Roadmaps to prevent creating multiple teams with exactly the same name.

Currently, users can create Shared Teams and plan-local teams with identical names, which leads to confusion and mistakes when selecting a team in the global Team field on issues.

The customer’s requirements are:

• Use a strict exact-match check (no fuzzy or “similar name” logic).

• Block creation of the new team if an existing team has the same name.

• Apply this behavior to all teams in Advanced Roadmaps (both Shared Teams and teams created within plans).

Expected Results

When a user creates a new team (of any type) in Advanced Roadmaps, Jira performs a strict exact-match name check against all existing teams.

If an exact‑match duplicate is found:

• The system blocks the creation of the new team.

• The user sees a clear error message stating that a team with this name already exists.

This logic applies to:

• Shared Teams

• All team creations inside Advanced Roadmaps plans (plan-local teams as well).

Actual Results

Users can create multiple teams (Shared and plan-local) with the same name in Advanced Roadmaps.

There is no validation to prevent duplicate names.

The Team field dropdown on Jira issues then shows multiple identical names, and users cannot easily tell which team is the correct one.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available