Hmm... I was gun ho to heavily promote the use of teams on temporary endeavors such as disappearing task forces, but now knowing that deleting the team once it is no longer in use will delete it from its associated tasks and projects, I'll have to temper my enthusiasm. I like the idea of team (and group) deactivation.
We have department leaving our instance and yet they have lots of teams which show up when you try to tag people in updates. Not a good experience for users.
There is more than one idea on this topic, so I am adding my vote & input here as well.
I don't understand how a system can offer agile, and require agile TEAMS in order to use the features, but not be able to sunset the teams. By definition, an agile development effort is finite. Once it ends, we get stuck with a dead team but we have to keep making them in order to do agile efforts. We have dozens needing deactivation at this point.
We also don't know the true impact of deleting a team, but we assume there will be to much history loss to consider it (membership, iteration details, etc). Sadly, some of our users supporting multiple agile efforts have 20+ teams (mostly dead agile teams) under their profile in order to preserve membership history.
That would be so useful. We don't wanna remove teams which we don't use currently. Would be much easier if we could deactivate. It wouldn't confuse people by still being in a dropdowns!
