• We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Atlassian status as of September 2019

      In Confluence 6.15 and earlier you can see a list of all pages that Confluence considers orphaned pages (not a child of a space homepage, and not linked to by any other page). Since the introduction of the Confluence 5 default theme, the orphaned pages screen has been less useful because it's always possible to see all pages in a space via Space Tools > Reorder pages.

      We removed the Orphaned pages screen in the default theme in Confluence 7.0.

      Feel free to comment on this issue if this change will have a significant impact on your Confluence site.

      Find out more about our other planned changes in Confluence 7.0

            [CONFSERVER-57601] Plans to hide the orphaned pages screen

            This has had a significant impact for our new users in particular.  Having a clearly defined tab helped them tremendously when they were reorganizing spaces and importing data.  I really hope it gets brought back.

            Janet Coffey added a comment - This has had a significant impact for our new users in particular.  Having a clearly defined tab helped them tremendously when they were reorganizing spaces and importing data.  I really hope it gets brought back.

            I don't like it either; however, Sharepoint isn't any better at this. If an upgrade broke any of your customizations, you'd have to get a developer involved to get it working again. 

            Southwest Reinsurance added a comment - I don't like it either; however, Sharepoint isn't any better at this. If an upgrade broke any of your customizations, you'd have to get a developer involved to get it working again. 

            So they take away a feature you paid for, then tell you to go buy it back from a third party. In what world does this make sense? 

            Gregory Muir added a comment - So they take away a feature you paid for, then tell you to go buy it back from a third party. In what world does this make sense? 

            They want you to go to the Atlassian store and buy a plugin now. Thankfully, there is one available called Cleaner.

            Southwest Reinsurance added a comment - They want you to go to the Atlassian store and buy a plugin now. Thankfully, there is one available called Cleaner.

            I would have to concur that the removal of this feature represents a mistake of staggering ignorance. how, pray tell, are we supposed to find orphans now? Foolishness. 

            Gregory Muir added a comment - I would have to concur that the removal of this feature represents a mistake of staggering ignorance. how, pray tell, are we supposed to find orphans now? Foolishness. 

            Cyrille Martin added a comment - - edited

            Hi Rebecca,
            I confirm you that the tab has been removed on the 7.1, 7.2 and 7.3 even if the documentation for those versions are still mentioning it

            Cyrille Martin added a comment - - edited Hi Rebecca, I confirm you that the tab has been removed on the 7.1, 7.2 and 7.3 even if the documentation for those versions are still mentioning it

            The documentation for 7.0 indicated that this tab would be removed. However, the documentation for 7.1 and 7.2 include info on the orphaned pages tab. Did Atlassian decide to leave the tab in place? We need to know before we plan an upgrade.

            Rebecca Brooks added a comment - The documentation for 7.0 indicated that this tab would be removed. However, the documentation for 7.1 and 7.2 include info on the orphaned pages tab. Did Atlassian decide to leave the tab in place? We need to know before we plan an upgrade.

            If you are going to remove this functionality then Atlassian should create some replacement tools instead of continuing the trend of offloading features to the Marketplace or just deprecating more functionality.

            Southwest Reinsurance added a comment - If you are going to remove this functionality then Atlassian should create some replacement tools instead of continuing the trend of offloading features to the Marketplace or just deprecating more functionality.

            But i do not see if a page has no incoming links on the reorder pages screen. This is a helpful information. Will you display this in any other way or have the space admins open every single "maybe orphaned" page and open the page information to check this manually?

            Tobias Ravenstein added a comment - But i do not see if a page has no incoming links on the reorder pages screen. This is a helpful information. Will you display this in any other way or have the space admins open every single "maybe orphaned" page and open the page information to check this manually?

            We use the orphaned pages screen frequently. It is an easy way to identify and edit orphans. Please retain access to this page.

            Rebecca Brooks added a comment - We use the orphaned pages screen frequently. It is an easy way to identify and edit orphans. Please retain access to this page.

            I concur also. I use it as Senior Administrator Confluence.

            Maciej Ląd added a comment - I concur also. I use it as Senior Administrator Confluence.

            The justification for removal is a logical fallacy.  In complex and dense spaces, reorder pages on its own has no indication as to which pages are orphans. It would be far more useful for the feature to remain and expanded to show all true orphans: Any page in a space which has no incoming link. A page that is a child of even the space homepage,  with no incoming links – a common situation with inexperienced users – is essentially invisible without perusing the page tree. Said inexperienced users (arguably, most users) won't go looking through page trees to see if they just happened to miss content.

            Cheetah Goletz added a comment - The justification for removal is a logical fallacy.  In complex and dense spaces, reorder pages on its own has no indication as to which pages are orphans. It would be far more useful for the feature to remain and expanded to show all true orphans: Any page in a space which has no incoming link. A page that is a child of even the space homepage,  with no incoming links – a common situation with inexperienced users – is essentially invisible without perusing the page tree. Said inexperienced users (arguably, most users) won't go looking through page trees to see if they just happened to miss content.

            I concur with Bill. I haven't needed this feature so far, but it seems like something that might be sorely missed one of these days.

            What about a compromise – replacing it with a "Highlight orphaned pages" button on the "Reorder pages" screen, next to the "Sort alphabetically" button?

            Piotr Janik added a comment - I concur with Bill. I haven't needed this feature so far, but it seems like something that might be sorely missed one of these days. What about a compromise – replacing it with a "Highlight orphaned pages" button on the "Reorder pages" screen, next to the "Sort alphabetically" button?

            I understand the motivation to making the UI cleaner, and makes sense for new users. But you are penalizing power-users with years of Confluence experience, who may use this feature infrequently, but then when they do, they have to hunt to figure out what happened to that tab. So much of what I do in Confluence is muscle memory.

            So when streamlining your product, put as much effort in to not penalizing your power users as you do in attracting new users, please.

            Bill Bailey added a comment - I understand the motivation to making the UI cleaner, and makes sense for new users. But you are penalizing power-users with years of Confluence experience, who may use this feature infrequently, but then when they do, they have to hunt to figure out what happened to that tab. So much of what I do in Confluence is muscle memory. So when streamlining your product, put as much effort in to not penalizing your power users as you do in attracting new users, please.

              Unassigned Unassigned
              rrobins Rachel Robins
              Votes:
              0 Vote for this issue
              Watchers:
              12 Start watching this issue

                Created:
                Updated:
                Resolved: