You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi team, my name is Kamil and I'm working as an Engineering Manager in one of DC cross-product teams.
We’re currently exploring the role archiving plays in managing your data in Jira, Confluence, and Bitbucket Data Center, and would love to hear about your successes and frustrations with archiving in Confluence!
Not sure where to start? Perhaps think about these questions:
Do the current Data Center archiving features meet your expectations?
What prevents you (or your team members) from archiving spaces, projects, or issues?
What would you like to see as the next improvement in archiving?
Do you use workarounds or other ways of marking your content as archived?
Hi Aron, please share! we'd be happy to hear any kind of feedback :)
Maybe the biggest problem we have seen over the years is that Confluence has not been strict enough (maybe in present tense?) about data validation.
This allowed users create corrupt data. For example, we have seen pages with NULL titles, page hierarchies with circular references (even pages that are parents of themselves), attachments without owning pages, etc.
This corrupt data can easily stay below the radar and won't hurt the end-user, but when the Better Content Archiving app tries to move those to the archive space, every sort of cryptic errors happen typically on the database level. The solution is querying the tables and fix the data, then retry the archiving, but this is extremely frustrating, time consuming and sometimes even risky. What makes it even worse is that the larger the Confluence instance is (the larger the customer is), the higher the probability of these... :-/