nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

moving this page

gordon grimes

This question is in reference to Atlassian Documentation: Moving a Page

Are there any plans to improve the "moving a page" feature such that some context is retained when I select "reorder pages"? 99% of the time I'm wanting to move either the page I'm on or the children of that page. As it stands I need to start from the top of the project and navigate my way back to the same page I'm on. At a minimum it'd be helpful to have a "jump to" dialog on the "reorder pages" top-level page so I could enter the name of the page I'm interested in.

Accepted answers

All comments

Stephen Deutsch

I find that reordering pages via the "Move Page" feature is way too difficult and you end up wasting a lot of time. If you want to reorder, your best bet is to Click "Space Tools" and "Reorder Pages" (if using the standard theme) or, if using the documentation theme, click "Browse", "Pages", and click "Tree View". Then you can reorder the pages simply by dragging and dropping them into place and you don't have to worry about losing the context.

Stephen Deutsch

Although it's true that you have to then find the page in the hierarchy that you wanted to move, it's usually not that bad to find the page, especially if you open the page reordering in a new tab.

gordon grimes

Thanks Stephen. Yeah, it's that 'navigating to the page' that I'm wanting to avoid. Our site has some deeply nested pages and since confluence hides stuff, like much of the path, re-navigating is an exercise. And it all seems pointless since confluence could easily know where to send me to start my reordering. True that sometimes I'm just wanting to reorder pages "generally", but even then being warped to my current page seems harmless enough and it is as likely to be "close" to my intended target as the root node is. I contend that sending uses to the root node is rarely what they need while sending them to the current node is nearly always what they need. The design chose the wrong default.

Stephen Deutsch

Hi Gordon,

I was looking around seeing if I could maybe fix this, and I found out that Confluence already has this feature, it's just super badly labeled. Under the Tools menu (or •••), there is an option called "View in Hierarchy". This is pretty much the exact same thing as reorder pages, but it will expand up to the part of the tree where your page is. How cool is that?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

confluence

page

move

feature

usability