Best Practice for decommissioning Groups

We were considering no longer using a group that has essentially become irrelevant to our processes. I was contemplating deletion of the group, archival of the group (remove members primary status and disconnect the associated application), possibly remove members completely and leave the group active, deactivate the group, or entertaining some other better method.  I just needed to understand best practice or things to consider when eliminating this group from the equation.  I don't wish to eliminate historical data, limit access to important information or complicate our analytical capabilities by doing the wrong thing. What are things to consider and if there are rules of thumb to keep in mind when making this decision I'd like to understand those considerations better?

Tags group groups Best-Practice
Asked by James Tiggett III on Thu 8/3/23 9:31 AM Last edited Thu 8/3/23 9:31 AM
Sign In to leave feedback or contribute an answer

Answer (1)

This answer has been marked as the accepted answer
Brittany Renn Thu 8/3/23 9:43 AM

Hi James, 

I would suggest removing the group as primary for users and then deactivating it until you know the group is no longer responsible for active items. You probably want to report on existing Tickets/Tasks/Project tasks/Issues/etc that they are responsible for before deactivating the group as well and you'd have to use the available report sources to do that. Once that is good to go, you could delete the group if you wanted, but you may want to just leave it deactivated just in case you ever want to report on historical data because you can still report on inactive groups.

Hope this helps but let me know if you have further questions! 

Best,

Brittany Renn

TDX Support

No feedback