Better Content Archiving for Confluence Server/Data Center: Feature Requests
- Ability to track which pages are expiring soon
- Send notification to recipients using an if-exists-otherwise logic
- Keyboard shortcuts for quick actions
- Check page view permissions before sending notifications to a user
- Make content searchable by publishing their status and other details as CQL fields
- Add a view to find and filter content owners
- Create a view to display a content owner's pages
- Register views from anonymous users
- Create a direct link between the fresh space and the archive space
- Provide REST API to page owner and page tree owner for a page
- Integration with Analytics for Confluence
- Split the concept of archiving configurations to separate the status rules from the notification scheme
- Customizable notification emails per space
- Provide REST API for global content quality statistics
- "Confirm" quick action for not viewed pages
- Do not overwrite already replicated pages when archiving descendants
- Display the content owner at a prominent place on the page
- Search and export contents by status
- Make archiving labels customizable
- Display the archiving date on archived pages
- Allow searching for pages with specific statuses
- Opt out of notification emails
- Allow configuring Confluence groups to notify
- Show display names instead of usernames in notification emails
- Add a new, visibly marked lifecycle state for "draft" content
- Dynamic expiry tracking (maybe using CQL?)
- Enforce global configuration in spaces, but allow space admins to start the archiving in their spaces
- Report of pages without content owners
- Tab navigation on the admin screen
- Allow users to set relative expiration date