You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 1, 2020. It is now read-only.
Handful of duplicate or otherwise inactive groups exist in the database. Ideally, these records (and any associated tickets) would be cleared from the platform after the group has been inactive for 30 days. The delete should cascade:
Remove related ticket files (including an S3 DELETE)
Remove related tickets
Remove related user memberships
Rake task can be scheduled with whenever to run periodically.
The text was updated successfully, but these errors were encountered:
Might be a good time to decide whether we want to implement soft deletion of any kind for future analytical purposes. It is sometimes nice to have historical data available to analyze.
Probably a good idea. I have the status flag on there that hides/deactivates things (tickets are instant delete). The buckets these fall into right now are: accidentally created groups (3) and guys who didn't like the service (1).
Handful of duplicate or otherwise inactive groups exist in the database. Ideally, these records (and any associated tickets) would be cleared from the platform after the group has been inactive for 30 days. The delete should cascade:
DELETE
)Rake task can be scheduled with
whenever
to run periodically.The text was updated successfully, but these errors were encountered: