Community
Q&A
Confluence
Questions
Moved page with folders to a new space - the child pages in folders were invisible

Moved page with folders to a new space - the child pages in folders were invisible

So - found a bug.

Moved a page from one space to another.

The page itself appeared in the new page, but the child pages didn't.

Quick investigation showed that in content manager there is a the main page, but clicking dropdown didn't show any pages.

refreshing page and ticking the box near the main page shows +N pages

clicking dropdown again shows no pages and tick shows +0 pages.

the pages were not orphaned and could be found via MCP

going to the page didn't show it in the UI - but moving it via contextual menu allowed it to be put under main page and show in UI.

Moving 40+ pages like this didn't seem like an option.

Tried seeing child pages via /child-pages block - found that all pages are 2+ levels deep. Meaning skipping something. Found that the skip was folders.

Using Gemini and Claude found a solution - use content -> reorder to move folders (and pages) to re-index them. Folders appeared in UI and pages were visible in the tree too.

Same happened in another space, but not sure if folders were involved or just simply moving it was a problem.

Previous tree structure -> Target tree structure

Content/page/page/folder or page -> Content/page/folder or page

Please see if it's reproducible and if it's a bug.

3 answers

1 accepted

1 vote

Answer accepted

@Siimon Härm ,

@Arkadiusz Wroblewski is right that this goes to Support, and @Mihai_LeanZero has the one tracked piece (CONFCLOUD-80330 explains why the Child pages macro skipped the folder level). Two things to add so the ticket lands as a bug rather than a how-to, and one documented cause to rule out first.

Rule out drafts before you report. Confluence cannot move unpublished content between spaces; a draft nested under a page or folder you move is not relocated, it is left behind in the source space with no warning. If any of the "invisible" pages were drafts or live-edit pages that had never been published, that part is by design, not a bug, and they are still in the source space's content manager. The published ones that went missing from the tree are the bug.

What you found is worth naming precisely for Support. The pages were not orphaned (you found them by ID and could move them individually), the tree showed +N and then +0 for the same node, and Content, Reorder repaired the tree without touching the pages. That pattern says the pages moved correctly and the tree index for the folder level did not get rebuilt during a cross-space move; Reorder forces the rebuild. Put those three facts, the source and destination space keys, the moved page ID, one child page ID that was invisible, and the timestamp of the move into the ticket. That is enough for them to pull the move event on their side, and it is the difference between a two-week ticket and a two-day one.

For anyone landing here with the same symptom: Siimon's workaround holds. In the destination space, Content, Reorder, then drag the affected folder (or any item) one position and back; the tree rebuilds and the children reappear. Do not re-move 40 pages by hand. And before any cross-space move of a tree that contains folders, publish every draft under it first, because those will not travel.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hey, @Sami Shaik, tried to, but couldn't for some reason select a correct board - which one should I use? Maybe you can suggest one.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Like • Sami Shaik likes this

@Siimon Härm , thanks for the accept, and the "cannot select the right board" moment usually has one of two causes.

1. The form is by product, not by topic. Go to support.atlassian.com/contact, choose Technical issues and bugs, then the product is Confluence (the cloud one, not Data Center), then your site from the list. The category after that is a routing hint, not a gate: pick the closest thing to pages or content and put the real description in the summary. Nobody at Atlassian rejects a ticket for a wrong category; they re-route it.

2. Your plan may not have technical support. This is the one that looks like "the option is missing." On a Free plan, Atlassian does not provide technical support tickets at all, only billing and account help, and the Community is the support channel. Standard gets tickets during business hours; Premium and Enterprise get 24/7. If you are on Free and the Technical issues path does not offer Confluence for your site, that is why, and the practical route is to post the evidence here (the move timestamp, both space keys, one affected page ID, and that Reorder repaired it) and, if you are willing, raise it on jira.atlassian.com as a bug report against CONFCLOUD, which any Atlassian account can do. A reported bug with a reproduction is worth more than a Support ticket for something Support would have to escalate to engineering anyway.

If you tell me which plan the site is on, I can be more specific about the path.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

0 votes

Hello @Siimon Härm

You should address that with support.atlassian.com

Best,

Arek🤠

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Thank you for response @Arkadiusz Wroblewski

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Like • Arkadiusz Wroblewski likes this

0 votes

Folders are the common thread here.

CONFCLOUD-80330 covers the child-pages part directly. The Child Pages macro cannot take a Folder as parent, and it errors outright when a page is converted to a folder after being set as one. Gathering Impact, 20 votes, open since December 2024. That accounts for what the /child-pages block did, though not for the tree itself.

The tree symptom I could not find tracked. Searched CONFCLOUD for child pages going missing after a move and the near matches are all about other things, so it reads as unreported rather than known.

The reorder fix is the useful clue. Reorder rewrites position, so if that alone brings them back the content was intact and the tree index was stale. Support will want precisely that: both space keys, roughly when the move happened, and that a reorder cleared it.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Thank you for response, @Mihai_LeanZero

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Suggest an answer

Was this helpful?

Thanks!

Confluence

DEPLOYMENT TYPE

CLOUD

PRODUCT PLAN

PREMIUM

We're moving! The community forums are migrating to a new platform on September 22. Learn more

Forums

Q&A

Community resources

Support

Top groups

Community resources

Support

Learn

Community resources

Support

Events

Community resources

Support

Moved page with folders to a new space - the child pages in folders were invisible

3 answers

1 accepted

Suggest an answer

Was this helpful?

Thanks!

DEPLOYMENT TYPE

PRODUCT PLAN

TAGS

Atlassian Community Events