-
Suggestion
-
Resolution: Unresolved
-
None
-
224
-
19
-
NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.
From a question in answers:
We recently ran into a problem in which an employee left our company and we lost some documentation for a team. Our confluence instance is tied to AD, so his account was deactivated. I ended up going through the AD team to reactivate his account, reset his password, then log in as him in order to see his drafts (which in turned allowed us to save some other content he had started but not saved). Is there no way for a Confluence administrator to view and delete drafts for a specific user? That feature would be incredibly helpful.
- is duplicated by
-
- Closed
- is related to
-
CONFSERVER-53589 Disabling Collaborative Editing feature does not remove existing shared drafts
-
- Closed
-
- is resolved by
-
- Future Consideration
- relates to
-
- Gathering Interest
[CONFSERVER-35921] Administrators should be able to see and delete drafts from all users
I have added a vote for this.
Any enterprise system with multiple users and employees who come and go MUST support the company that owns the system and pays its employees to document access to everything.
Once an employee enters data in Confluence, the company owns that information, which is regarded as IP.
I'm all for security; however, a company admin should always be able to access everything: all drafts, all restricted pages, and everything else.
TIA
Can someone share the SQL query to get the drafts older than 6 months?
- 394.206 (# of regular Drafts Attachments older 6 months)
- Potential free-up Space from FS ~184GB
- It's Crazy that no mechanism from a tool is given to provide this basic feature... built in, instead of DB deletion and corresponding FS removal
- A disappointment and typical, a pressure to cloud, once more...
We just discovered 50,000 drafts (plus 180,000 associated attachments) in one of our instances, so yes please - either allow admins to see all the drafts without going into the database, or allow us to set guardrails that remove drafts that haven't been touched in X amount of time.
Running into issues with this again. Hidden drafts that need to be deleted before pages can move between spaces, and we've got to try and get the person who created them to delete them rather than just have an admin delete them.
Waste of everyone's time.
The reason we care is that a page with an unpublished child has a drop-down arrow next to it in the left-hand navigation pane; but clicking on that arrow does nothing, because there are no new pages to display (because they are only in draft).
So Confluence knows that draft exists; it just chooses not to allow Admins to see it because... ?
9 years ago someone posted a series of database commands you could use to assign one person's drafts to yourself, so you could edit and delete them. 9 years later Confluence is still unable to provide the most basic controls. Oh, right, because someone wrote an app to fix it.
If you added up all the apps you need to buy to fix the basic bugs in the simplest use of Confluence, I wonder how much the monthly user fee would be?
We are in the middle of a large migration to confluence cloud. Not having this feature means we are moving 10's of thousands of unpublished (and likely empty) pages to the cloud, costing us real, measurable downtime and money.
Having this ability would have allowed our admins to do a massive cleanup and saved us tons of time, money and risk avoidance.
+1
this feature is needed