Team: Multiple Teams With Same Name

[JamesonRGrieve]

Description:

The system allows the creation of a new team with a name that already exists. There is no validation to prevent duplicate team names.

---

Steps to Reproduce:

1. Login to Dev UI server
2. Navigate to Team management > Team
3. Enter a team name that already exists in the system.

---

Expected Behavior:

The system should validate and prevent duplicate team names, showing an appropriate error message like:

"Team name already exists. Please choose a different name."

---

Actual Behavior:

A new team is created with the same name

---

Impact:

Can lead to multiple teams with the same name, making it difficult to differentiate.

[JamesonRGrieve]

Clarification - this should be validated on the front end IE "You are already a member of a team with this name, creating another may cause confusion, are you sure you want to continue?"

This should not be a unique constraint in the database or anything like that.

[yogeshCelestial]

@JamesonRGrieve,

If multiple users become a part of both same same-named teams, it will create a lot of confusion for them to differentiate or likely be impossible.
Team Title should be a unique entity, like a username; if one takes it, the same can't be taken by another.

[yogeshCelestial]

@JamesonRGrieve ,

We have done as per your requirement and raised a PR - #59

[SumanaRameshBaswan]

@JamesonRGrieve, the implementation has been done based on your comments. However, this approach might lead to confusion going forward. Could you please confirm if this is the intended behavior?

[yogeshCelestial]

@SumanaRameshBaswan, if you have verified this work, please mark it as complete.

[SumanaRameshBaswan]

@yogeshCelestial , I have verified and the feature is working as per James requirement. However, I would like to confirm if this behavior fully aligns with his expectations before proceeding further.
@JamesonRGrieve I want to bring your attention to a potential issue that could arise if this is left as-is:

Allowing multiple teams to have the same name introduces several usability and data integrity challenges

1. UI Ambiguity: Users (nurses) may not be able to distinguish between teams with identical names when selecting from dropdowns or during CSV resident uploads.
2. Incorrect Data Mapping: Notes, conversations, or resident records may be mistakenly associated with the wrong team if the name is used for identification.
3. Invitation Confusion: Users may send/ receive invites to similarly named teams and mistakenly join the incorrect one.
4. Logs and support issues become harder to trace when teams are not uniquely identifiable.

@jnelsoncelsys