-
Suggestion
-
Resolution: Unresolved
-
12
-
9
-
Hello everyone,
I'm April, a product manager looking after Atlassian Teams 👋. I appreciate you sharing your insights and use cases regarding the problem around duplicate Teams, thank you for your feedback.
We recognise the importance of addressing this problem and we are looking to explore it further in the upcoming 18 months - there are some improvements that may tangentially address this problem. This is still in the early stages and isn't part of our roadmap yet. For this reason, I'm moving this to the 'future consideration' phase. I'll provide an update in a few months on where this is at 🙏
Please feel free to continue to provide feedback on this suggestion in the comment thread below if you believe this is an important ticket to address. We will take this into account during prioritisation discussions.
Best regards,
April
Summary
Jira users are currently able to create teams with duplicate names, which may not be desired by some Jira admins as it can cause confusion to the users when searching, filtering, and creating reports using the Team name as a parameter.
Steps to Reproduce
- On Jira Software, select Teams > Create a Team
- On Team name, enter the name of a team that already exists.
- Select Create a team
- Team is successfully created.
Suggested Solution
- Jira admins would be able to determine if duplicate team names should be allowed or not.
OR - Users would not be able to create a team if the team name already exists.
Current Workarounds
- Jira admins need to manually monitor for teams recently created and verify if a duplicate name has been used.
- duplicates
-
- Not Being Considered