Hi everyone,

Thank you for previously raising this bug and bringing it to our attention.

Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Confluence users.

As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know.

Thank you again for providing valuable feedback to our team!

In Confluence 5.9.5 I had to leave the tab open with the moving dialog (not hit Cancel or anything) and wait like 1 hour - afterwards the page tree was moved - annoying!

I have also experienced this problem. We are running V5.8.9
Agree. The behavior is very frustrating and makes us the admins waste lots of time. I hope Atlassian fixes this problem soon.

the current behaviour is quite misleading and poor. I had the situation where:

1. i started the move of a page (it had some 3000 child pages)
2. this failed after ~ 1 minute. I thought it had stopped
3. then i started noticing that attachments were not available on some pages. I thought it had partially transferred files then failed. So started looking at recovering the confluence attachment file system from a backup (which is a huge deal for us)
4. 1.5 hrs later it mysterious completed and the page had been moved and attachments had worked

Clearly it was working in the background.

I had the same Timeout Error problem while moving a page with many children to a new space. If I leave the "Move" window open after the Timeout Error appears the move process does continue. Don't close the move window even though it generated the error. Click on "Durchsuchen" or "Browse" and navigate to the intended destination. The destination should populate and update as the move on the backend continues. You may need to click on Search and go back to Browse in order to see the updates.
This is a bug for sure, but hopefully my work around can help.

Andreas, see https://jira.atlassian.com/browse/CONF-34233 . Some timeout ends and gives you the error, although the page hierachy is moved. It took hours to move our hierarchies in our site, but they were moved. We have Confluence 5.4.4.
I suggest you to raise a support ticket at Atlassian if you need more explanation on this.

The same happens while moving a page to a different place in the tree within the same space. In the tree view i do the moving but when i refresh the page it is again at its earlies place. And the same log appears. I think it is a major bug.