-
Suggestion
-
Resolution: Duplicate
-
None
-
None
NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.
A customizable "Empty trash" mechanism which would automatically purge from each space trash all deleted files whose deletion is dated before a customizable time range value. The frequence of the purge could also be customizable.
The function would be customized through the following interfaces:
- a site admin interface where site-wide defaults are defined (with "Never purge" as a possible choice)
- a space admin interface where site-wide defaults can be overridden by local values
Advantages of regularly purging deleted pages through such a mechanism would include:
- releasing unneeded data and database space
- preventing side effects and problems, such as the one documented in Page cannot be moved between spaces due to existing duplicate in trash
- eliminating the time-consuming (and needless) chore for admins to manually sort and purge deleted files
- by-passing a limitation of the present "Trash" listing, where there is no "Deleted on" column on which a selective purge could be based
- duplicates
-
CONFSERVER-18160 Allow Confluence to auto purge trash over a period of time
- Closed
- relates to
-
CONFCLOUD-36075 Empty space trash automatically.
- Closed
[CONFSERVER-36075] Empty space trash automatically.
Workflow | Original: JAC Suggestion Workflow 4 [ 3564823 ] | New: JAC Suggestion Workflow 3 [ 4340467 ] |
Workflow | Original: JAC Suggestion Workflow 2 [ 3186201 ] | New: JAC Suggestion Workflow 4 [ 3564823 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: JAC Suggestion Workflow [ 3027611 ] | New: JAC Suggestion Workflow 2 [ 3186201 ] |
Workflow | Original: Confluence Workflow - Public Facing v4 [ 2536766 ] | New: JAC Suggestion Workflow [ 3027611 ] |
Workflow | Original: Confluence Workflow - Public Facing v3 [ 2301472 ] | New: Confluence Workflow - Public Facing v4 [ 2536766 ] |
Workflow | Original: Confluence Workflow - Public Facing v3 - TEMP [ 2198513 ] | New: Confluence Workflow - Public Facing v3 [ 2301472 ] |
Workflow | Original: Confluence Workflow - Public Facing v3 [ 1942260 ] | New: Confluence Workflow - Public Facing v3 - TEMP [ 2198513 ] |
Workflow | Original: Confluence Workflow - Public Facing v2 [ 1751493 ] | New: Confluence Workflow - Public Facing v3 [ 1942260 ] |
Description |
Original:
A customizable "*Empty trash*" mechanism which would automatically purge from each space trash all deleted files whose deletion is dated before a customizable time range value. The frequence of the purge could also be customizable.
The function would be customized through the following interfaces: * a site admin interface where site-wide defaults are defined (with "Never purge" as a possible choice) * a space admin interface where site-wide defaults can be overridden by local values Advantages of regularly purging deleted pages through such a mechanism would include: * releasing unneeded data and database space * preventing side effects and problems, such as the one documented in [Page cannot be moved between spaces due to existing duplicate in trash|https://confluence.atlassian.com/x/r4QtKQ] * eliminating the time-consuming (and needless) chore for admins to manually sort and purge deleted files * by-passing a limitation of the present "Trash" listing, where there is no "Deleted on" column on which a selective purge could be based |
New:
{panel:bgColor=#e7f4fa} *NOTE:* This suggestion is for *Confluence Server*. Using *Confluence Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/CONFCLOUD-36075]. {panel} A customizable "*Empty trash*" mechanism which would automatically purge from each space trash all deleted files whose deletion is dated before a customizable time range value. The frequence of the purge could also be customizable. The function would be customized through the following interfaces: * a site admin interface where site-wide defaults are defined (with "Never purge" as a possible choice) * a space admin interface where site-wide defaults can be overridden by local values Advantages of regularly purging deleted pages through such a mechanism would include: * releasing unneeded data and database space * preventing side effects and problems, such as the one documented in [Page cannot be moved between spaces due to existing duplicate in trash|https://confluence.atlassian.com/x/r4QtKQ] * eliminating the time-consuming (and needless) chore for admins to manually sort and purge deleted files * by-passing a limitation of the present "Trash" listing, where there is no "Deleted on" column on which a selective purge could be based |
Link |
New:
This issue relates to |