• 0
    • 2
    • 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.

      NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.

      I don't know how Confluence handles web requests under the covers, but some of our users have asked whether this feature exists in Confluence (we just moved from Trac). I have since found that it doesn't. In Trac, if you have a page hierarchy like so:

      • Page1
        • Page1Child
      • Page2
        • Page2Child
          • Page2ChildsChild

      You could access Page 2 Child's Child like http://trac/Page2/Page2Child/Page2ChildsChild and Page 1's Child like http://trac/Page1/Page1Child and so on and so forth. This is very user friendly because the URL actually means something to them.

      However, in Confluence the page hierarchy as far as URLs is completely flat. The major reason we want this is because we have multiple projects per space to cut down on the sheer number of spaces we would need. For example, if we have test reports we'd like to be able to have multiple pages called 'Introduction' in the same space, as long as there wasn't already a page with that name under that level of the hierarchy (i.e. the same parent). Having to name my page 'Project 1.4.6 Test Report Introduction' is a bit extreme, not to mention ugly when you export the page hierarchy to PDF for external consumption, as the table of contents is derived from the page titles.

      Now that I think about it, this may be two feature requests...

      1. The ability to access a page using its hierarchy in the URL and
      2. The ability to have multiple pages of the same title in the same space, enforced by parentid.

            [CONFSERVER-18089] Ability to access pages by hierarchy in the URL

            robert added a comment -

            It is very hard. This is my biggest issue with the design of confluence and it really limits it's flexibility.

            robert added a comment - It is very hard. This is my biggest issue with the design of confluence and it really limits it's flexibility.

            vote for this. We came to situation when we have a lot of pages in a single space and sometimes flat URIs make it really tough to think out unique titles for every next page. Having hierarchy can make it a lot easier

            Irina Pykhova added a comment - vote for this. We came to situation when we have a lot of pages in a single space and sometimes flat URIs make it really tough to think out unique titles for every next page. Having hierarchy can make it a lot easier

            Ubloobok added a comment -

            Vote many times for this feature, because human readable links are very useful for well structured documentation.

            Ubloobok added a comment - Vote many times for this feature, because human readable links are very useful for well structured documentation.

            Still waiting for this feature. A huge limitation if you ask me, and so important for some that it becomes a dealbreaker when using Confluence.

            frederikt2trace added a comment - Still waiting for this feature. A huge limitation if you ask me, and so important for some that it becomes a dealbreaker when using Confluence.

            Our use case is one Confluence space per department of a company.

            There's larger departments that consist of multiple teams; that would work better with natural URL navigation (hierarchy in URL). Doing so would clearly show that you are viewing a page representing a team within a department.

            Chris Hamilton added a comment - Our use case is one Confluence space per department of a company. There's larger departments that consist of multiple teams; that would work better with natural URL navigation (hierarchy in URL). Doing so would clearly show that you are viewing a page representing a team within a department.

            Another yes vote here to have this feature

            Daniel Allen added a comment - Another yes vote here to have this feature

            I would like confluence to have this feature

            Robert Metcalf added a comment - I would like confluence to have this feature

            jason_s added a comment -

            Since CONF-2524 got closed with Won't Fix it seems like this one's dead in the water also. >

            jason_s added a comment - Since CONF-2524 got closed with Won't Fix it seems like this one's dead in the water also. >

            Braxton Ehle added a comment - - edited

            Any update on the priority of this work? This would be a hugely helpful thing to see implemented for all the reasons mentioned above.

            Braxton Ehle added a comment - - edited Any update on the priority of this work? This would be a hugely helpful thing to see implemented for all the reasons mentioned above.

            The lack of hierarchy in the URL is one of the biggest limitations as far as I'm concerned. Having several pages named "API" or "FAQ" within one space is nothing exotic.

            Bertrand Dunogier added a comment - The lack of hierarchy in the URL is one of the biggest limitations as far as I'm concerned. Having several pages named "API" or "FAQ" within one space is nothing exotic.

              Unassigned Unassigned
              e27ef199b8f6 Matthew Baker
              Votes:
              36 Vote for this issue
              Watchers:
              31 Start watching this issue

                Created:
                Updated: