As a user, I'd like the archiving to skip those parent pages that have any children not going to be archived in the same lifecycle to preserve original structure (i.e. to avoid moving children up in the page hierarchy).
Do not archive parent page if there's any children not to be archived
Have more questions? Submit a request
-
Dirk Disch We at SICK AG (www.sick.com) would like to keep the same structure in the archive space as well as in the fresh space. Archiving parents if they already have children that are not archived destroys the space structure, especially if parents are used to structure children pages and give an overview about them.
-
Aron Gombas Dirk, it is a bit unclear what'd be the expected behavior for you.
If page "A" should be archived, but its child "B" should not, then what do you expect? "A" will not be archived either? Something else?
-
Dirk Disch Hello Aron,
in your described case (If page "A" should be archived, but its child "B" should not, then what do you expect?) My expected behaviour would be as you stated "A" will not be archived either"
Another example: Page A has childs B and C.
Page A should only be archived, if Page B and C are archived, too. This avoids that the space structure may be destroyed.Page A ("Minutes Overview")
|- Page B ("2020-04-29 team minutes")
|- Page C ("2020-04-28 team minutes")
Or a more specific example: Page A is an overview page for meeting minutes. It gatheres its information dynamic e.g. via metadata or child-macros. Therefore this page might not be edited for a very long time. If I have an archive rule based on last edits, than someday the overview page is archived and plenty of single minutes pages are appearing one level up without the structure/overview page.
In this simplified case I could use "noarchive-single"at the overview page, because the overview is a permanent page, but I have many use cases, where this is not possible (but would be more difficult to explain briefly)I think it would be beneficial to have an option in the archiving configuration where I could enable, that parent pages are skipped if any children are not archived.
Is the expected behavior now clear for you?
-
Aron Gombas Thanks, Dirk, I understand.
I will keep this here and will see what other users react, because I think this behavior would confuse others. But, as you pointed out, it could be optional.
-
Dirk Disch Aron, yes I agree. Depending on the space structure (and the amount of pages in a single space) this might be confusing. We have quite big spaces with a complex structure.
I think to have it optional would be best for all users. -
Angela Gleissl This feature is quite important to us as well. We are losing the structure of our spaces. This is actually a no go for us and we're looking for alternatives to the plugin right now.
Some of our users enumerate the page tree and their enumeration gets messed up. Also some users aggregate data over long period of time in parent pages. If those parent pages are archived, this is quite annoying.
-
Renni Verho Hi,
got info about noarchive option ( https://midori-global.com/products/better-content-archiving-for-confluence/server/documentation/page-archiving ) for other issue.
That could work for example case if Page A is marked with noarchive label.
Page A ("Minutes Overview")
|- Page B ("2020-04-29 team minutes")
|- Page C ("2020-04-28 team minutes") -
Wesley Tuscano Voting for this feature.
-
Karen Leonardi voting for this feature. Surprised to learn that parents are archived when they have children that will not be archived when archiving job runs. Understanding there is an option when you set a page to archive, to include/exclude descendant pages, seems this could be represented with a different archiving tag. Whereas for those pages that are picked up for archive based on rules set for the archive, leaves us with an unknown as to how many child pages will lose their parents, thus impacting the page tree structure.
-
Tugs Parra Absolutely need this feature - voting for it!
-
Raymond Santangelo I don't know if the developers at Midori appreciate the havoc it causes when parent pages are moved to the archive due to meeting criteria like "page has not been viewed in 365 days" when such parent pages have "fresh" child pages. In case it is not clear from Ferenc's initial post, such child pages are left "orphaned" in the fresh space (technically, they are left located under the "grandparent" page in a disorganized structure, which is perceived as "orphaned" or "messed up" by most users). Perhaps there is a reason why you would want to archive a parent page in this situation, but I cannot think of a good one -- at the very least, there should be a configurable option to allow space admins to "skip parent pages with fresh children" when running an archive job.
-
Levente Szabo Hi Raymond and all participants here,
Yes, we are aware of the importance of this request.
While I can't share a planned release date, rest assured that this is part of the roadmap and the product team will get around to take a look at possible solutions.
For the time being, you can consider marking your parent pages with the "noarchive-single" label that would prevent archiving the parent pages (and would also exclude those from lifecycle checks).
We appreciate your feedback and continuous patience with us!
-
Raymond Santangelo >> For the time being, you can consider marking your parent pages with the "noarchive-single" label that would prevent archiving the parent pages
Thank you for tip, Levente... just note that our Confluence instance has over 35,000 pages for our team alone, so this approach does not scale well for our team, let alone our company. (I do appreciate the suggestion, though; we have already applied this workaround to our most important branches.)
-
Stella Schneider We need this feature as well.
The workaround is also not possible for us, since every space has a certain structure with crucial parents, meaning we would need to set the label to over 2000 pages manually....
-
Gary Spross Any word on the status of this feature? Having this option would be really beneficial.
-
Lance Swaim Please get this implemented as it's causing confusion for our users.
-
Raymond Santangelo Hi Levente,
Looking at your previous post from March 6, 2024, you had written, "rest assured that this is part of the roadmap". That was quite a while ago ... can you please give an update on this?
I continue to hear from our users about this issue.
Thank you,
Ray
Please sign in to leave a comment.
17 Comments