Data Retention on messages and contacts

[kurtsudonumcom]

Is your feature request related to a problem? Please describe.
Users are frustrated when they performing searches and this may result in a timeout their lookup - cause of having too much messages stored.

Describe the solution you'd like

Data detention features that includes:

1. an expiry of messages older than a threshold i.e. 30, 90 days etc. and
2. To clear out conversations with no messages attached,
3. Deleting contacts for inactivity; being part of a conversation thread of no messages older than a particular threshold.

Other throughts

• It would be great here to have a Macros utilise the delete message, or
• automation on deletion, and
• default policy of data retention (off by default or default value)

Describe alternatives you've considered
A cronjob doing requests on the delete message endpoint. We had to batch this job to delete older messages going back years.

Additional context
Of course, increasing the RAM on the db would yield better results, however I feel this project could provide features on the granularity of data that can be kept or retained - as suppose to keeping everything.

[SamsungGalaxyPlayer]

I too would like a standard records retention policy. It would be good to be able to easily set an administrator setting in the UI to auto-delete all tickets that don't have any activity for over X days, for example.

[jordan26]

+1 on this, considering GDPR and other reasons, we really need the ability to easily delete (in bulk/automatically) older messages!