Team deletion without needing to find every project linked to that team

[nicolelaine]

Is your feature request related to a problem? Please describe.
As it stands, if one wants to delete a team on the Tasking Manager, it's not possible unless you find every single project that team has ever been linked to, and then unlink that project first. However, there is no link to any list with the projects that have been linked, making this a bit of an impossible task. As a result, there are defunct teams on the Tasking Manager that cannot be easily deleted.

Describe the solution you'd like
Be able to delete a team on the Tasking Manager without needing to find every project this team has ever been associated with and unlink it.

[ramyaragupathy]

For team managers:

• The Projects section should list all linked projects categorized as Published, Draft and Archived
• Include an “Unlink all projects” button at the top.
  • On click: Show confirmation prompt → “Are you sure? This action cannot be reverted.”
  • On confirmation: All projects are unlinked in one action.

For other logged-in users:

• The Projects section should display only published projects.
• No unlink or other management options visible.

cc @royallsilwallz @manjitapandey

[ramyaragupathy]

Points raised by @prabinoid during the discussion:

• any team (public or private) can be linked to any project.
• team managers may not have project edit access.
• similarly org managers can only edit projects linked to their own organisation.
• they cannot unlink teams from projects linked to other orgs, they would need project edit access to do so.

Questions:

• Should team managers be allowed to unlink projects they can’t otherwise edit?
• or should unlinking a project from a team require:
  1. Team manager permissions plus
  2. Project edit permissions?
• or should we allow both team managers and org managers (of the team’s org) to unlink projects from teams, even without project edit rights?

cc @royallsilwallz @manjitapandey @Ashik-AD @suzit-10

[manjitapandey]

While unlinking projects
During project editing, permission set as team members can be saved without adding any team. Is this expected??

[prabinoid]

We could check if the project has the teams mapping and validation permission and if so prevent the team unlinking until a different team is assigned to the project or permission is changed. But it would undermine the whole point of introducing this feature for the team managers unlinking their team from a certain project irrespective of the project permission.

[emi420]

Maybe you can mark the team as deleted but not delete the row in the DB.

[ramyaragupathy]

Thanks for flagging the issue @manjitapandey.

The endpoint should verify if there are more than one teams attached to a project in a particular role.

• If only one team is attached in that role, show a warning to the user:
  "This project has mapping/validation permissions restricted to teams, but no other team is assigned. Please contact the project author before unlinking."
• If multiple teams are attached, then allow unlinking normally.

This prevents situations where mapping/validation permissions remain set to "teams" but no relevant teams are actually attached.

Please see my proposed layout with bulk unlinking action included.

PROJECTS                                    [View All]   [Unlink All]
[Published] [Archived] [Draft]
---------------------------------------------------------
[x]  new test project       [View] [Unlink]
[x]  another project        [View] [Unlink]
---------------------------------------------------------
[Unlink Selected]   (appears only when checkboxes are ticked)

@prabinoid @suzit-10