• 9
    • 16
    • 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.

      Adding the ability to nest spaces would be a great thing for us. We want each of our consulting projects to have its own space (so it can have its own blog, namespace, permissions etc.) but we don't want to have hundreds of spaces when you look at the list.

      It would also allow us to give administrative rights for broad areas to different people (e.g. Bob can administrate the "Projects" space, and all the spaces under it, but he can't administrate the "Sales" space).

      It could possibly be used as a way to give personal spaces also - having a "Personal" parent space, with everybody's individual spaces underneath that organised however necessary (with us it would probably be by office location).

            [CONFSERVER-1095] Nested Spaces

            Marc Moroz added a comment -

            This would really help with organization.  Many features for spaces are nice but you don't want everything at the top level.  A way of group or creating a space hierarchy would be great.

            Marc Moroz added a comment - This would really help with organization.  Many features for spaces are nice but you don't want everything at the top level.  A way of group or creating a space hierarchy would be great.

            This is painful for end users.  Can someone put this forward as a ship-it idea for the next Global ShipIt?   

             

            Atlassian exists to unleash the power of teams, and to do so companies need standardized document trees at times for projects.  We cannot standardize document trees without this feature, which means we (customers in general) cannot scale with Confluence as it exists today.

            Deleted Account (Inactive) added a comment - This is painful for end users.  Can someone put this forward as a ship-it idea for the next Global ShipIt?      Atlassian exists to unleash the power of teams, and to do so companies need standardized document trees at times for projects.  We cannot standardize document trees without this feature, which means we (customers in general) cannot scale with Confluence as it exists today.

            We def have a need for repeating page titles within one space for projects etc and I'd have thought this would be very common for customers.
            We use a lot of Atlassian apps and they're great but this issue is a constant annoyance for staff. However reading through the comments from the vendor I don't think Atlassian understands the issue, the worry about search results seems odd and I agree with the customer comments above.

            My main concern is this the age of this ticket and currently "NOT BEING CONSIDERED". Only 300+ Votes - unsure number needed to get their proper attention. I'm hoping there is a duplicate ticket for this thats actually in development and this status here not updated? 

            Can someone from Atlassian at least make a comment on here that this is being reviewed?

            Many thanks.

            David Chapman added a comment - We def have a need for repeating page titles within one space for projects etc and I'd have thought this would be very common for customers. We use a lot of Atlassian apps and they're great but this issue is a constant annoyance for staff. However reading through the comments from the vendor I don't think Atlassian understands the issue, the worry about search results seems odd and I agree with the customer comments above. My main concern is this the age of this ticket and currently "NOT BEING CONSIDERED". Only 300+ Votes - unsure number needed to get their proper attention. I'm hoping there is a duplicate ticket for this thats actually in development and this status here not updated?  Can someone from Atlassian at least make a comment on here that this is being reviewed? Many thanks.

            The lack of this simple utility will probably burn my choice of confluence as a documentation tool. I need to be clear when presenting the tool to the group to justify the price and not to hide this gap

            Eduardo Santos added a comment - The lack of this simple utility will probably burn my choice of confluence as a documentation tool. I need to be clear when presenting the tool to the group to justify the price and not to hide this gap

            Hey guys, I've been meaning to move my companies workflow over from Notion which allows this. There is also an up-and-coming product called Coda Coda which I've tested and also has this functionality. It'd be great for you to re-consider because right now it's very annoying having to try and come up with unique page names, especially when they're nested under other pages.

            Garry Taulu added a comment - Hey guys, I've been meaning to move my companies workflow over from Notion which allows this. There is also an up-and-coming product called Coda  Coda which I've tested and also has this functionality. It'd be great for you to re-consider because right now it's very annoying having to try and come up with unique page names, especially when they're nested under other pages.

            Daniel Clayton added a comment - - edited

            I was really surprised to see a title of a document dictate it's uniqueness across a space. In order to make the title unique, the Space Tree and URL both are not pretty. And this is just to support search?

            • Project A
              • Project A / Introduction
            • Project B
              • Project B / Introduction

            url: .../pages/viewpage.action?pageId=101274033

            IMHO, I'd rather see duplicate Introduction results with urls below each.

            Introduction
            .../pages/Project A/Introduction

             

            Actually, naming the url from the title forces us to break references if we change the title. Having control over the url name would be better.

            Daniel Clayton added a comment - - edited I was really surprised to see a title of a document dictate it's uniqueness across a space. In order to make the title unique, the Space Tree and URL both are not pretty. And this is just to support search? Project A Project A / Introduction Project B Project B / Introduction url: .../pages/viewpage.action?pageId=101274033 IMHO, I'd rather see duplicate Introduction results with urls below each. Introduction .../pages/Project A/Introduction   Actually, naming the url from the title forces us to break references if we change the title. Having control over the url name would be better.

            This is a big one. I was surprised to see that there is no way around this except creating cumbersome page names. I want to publish different benchmark results for different machines at work, and this simple task becomes a naming nightmare because I can't do something as simple as scenario1/machine1/benchmark1. Also this problem makes copying pages with children virtually impossible, meaning I have to copy several pages one by one.

            Gino McEvoy added a comment - This is a big one. I was surprised to see that there is no way around this except creating cumbersome page names. I want to publish different benchmark results for different machines at work, and this simple task becomes a naming nightmare because I can't do something as simple as scenario1/machine1/benchmark1. Also this problem makes copying pages with children virtually impossible, meaning I have to copy several pages one by one.

            glenn added a comment -

            ARGH! you guys seriously need to re-consider this. It's very difficult to find / organize information in a space for a team when we discuss multiple project.

            glenn added a comment - ARGH! you guys seriously need to re-consider this. It's very difficult to find / organize information in a space for a team when we discuss multiple project.

            Thanks for your interest in this issue.

            While this suggestion has gathered significant interest, we're unable to implement all of the excellent suggestions you make. We appreciate the benefits of such requests, but don't plan to work on this for the foreseeable future.

            This suggestion will be reviewed in about 12 months time, at which point we’ll consider whether we need to alter its status.

            Jenny (Inactive) added a comment - Thanks for your interest in this issue. While this suggestion has gathered significant interest, we're unable to implement all of the excellent suggestions you make. We appreciate the benefits of such requests, but don't plan to work on this for the foreseeable future. This suggestion will be reviewed in about 12 months time, at which point we’ll consider whether we need to alter its status.

            any update?

            Yarden Gerecht Yaron added a comment - any update?

              Unassigned Unassigned
              d2fcb6d09ba3 aidan
              Votes:
              342 Vote for this issue
              Watchers:
              147 Start watching this issue

                Created:
                Updated: