That's not actual archiving, but in some case this is needed for legal reasons.
Source: https://community.atlassian.com/t5/Confluence-questions/Solution-for-automated-trash-purging/qaq-p/689230
That's not actual archiving, but in some case this is needed for legal reasons.
Source: https://community.atlassian.com/t5/Confluence-questions/Solution-for-automated-trash-purging/qaq-p/689230
We not only need to be able to delete archived content after a period of years to clear space, but for legal/regulatory reasons as well.
An end-user describe his use case as:
End of life would be, when a content item is in an archive space and not updated in 8 years. Being in an archive space would imply not being viewed. The time values would need to be parameters in the config one would assume.
My idea for end of life action is to have a "Final Resting Place" (FRP) space, which could be deleted manually or possibly as part of the archiving process, and recreated upon need for more pages to delete.
Hi all,
Some weeks ago we published a guide for implementing "permanently delete" type archiving strategies. I hope this helps.
CLOUD UPDATE
Just very recently we released a new automation action "Purge" in the Confluence Cloud version of the app. It allows periodically purge (permanent removal) contents from your site using an automation! Therefore, it is the equivalent of the "permanently delete" archiving strategy in the cloud version.
👉 Learn more in the app documentation.
Notes:

4 Comments