-
Suggestion
-
Resolution: Fixed
-
2
-
9
-
NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.
If attachment versions are older than a specified time they should optionally either deleted or archived
- incorporates
-
CONFSERVER-21373 No limits on historic attachments
-
- Closed
-
- is related to
-
CONFSERVER-7259 Add administrator ability to monitor attachment statistics by user
- Closed
-
CONFSERVER-26182 Provide XML-RPC method for removing an attachment version
- Closed
- relates to
-
CONFCLOUD-7260 Ability to specify maximum number of attachment versions and expiry date (Attachment Archive Control)
- Closed
-
CONFSERVER-7258 Allow configuration of maximum attachment sizes per space or per page
- Closed
-
CONFSERVER-8469 Have ability to set the maximum number of attachments per page on a space by space basis
- Closed
-
CONFSERVER-23873 Allow to set maximum number of Attachment Versions
- Closed
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Wiki Page Loading...
Hi everyone,
This is Jacqui from the Confluence team. I'm pleased to let you know that we released retention rules in Confluence DC 7.16, enabling the automatic cleanup of historical data. You can tell Confluence how many attachment versions you want to keep (by number or age of the versions), and then a scheduled job will delete the excess, in small batches, so as not to impact your site's performance. Here's the full documentation for how this feature works if you wish to explore further.
Thanks to all those who waited for this feature, we hope you find it useful when administrating Confluence DC.
Kind regards,
Jacqueline Bietz
Associate Product Manager
Confluence Data Center