-
Suggestion
-
Resolution: Unresolved
-
3
-
16
-
NOTE: This suggestion is for Confluence Cloud. Using Confluence Server? 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).
Hi everyone- I’m DJ Chung, a PM on the Confluence team. We know this is a very popular request, but this is a feature that we don't have plans to prioritize in the near future. We will provide updates on this feature request as we have them.
If you'd like to chat more about this, please feel free to find with me here: https://calendly.com/djatlassian/30min
- is duplicated by
-
- Closed
-
- Closed
- is related to
-
- Closed
-
- Closed
-
- Closed
-
- Not Being Considered
- relates to
-
- Closed
-
- Closed
-
- Gathering Interest
- mentioned in
-
Page Loading...
-
-
-
-
-
-
[CONFCLOUD-1095] Nested Spaces
I would like to add my 2 cents to the discussion. I've read [this page|https://community.atlassian.com/t5/Confluence-Cloud-questions/Pages-with-same-name-in-space/qaq-p/443236] with a whole discussion similar to this which states that having the same name for a page is not supported because it breaks search. So this hiearchy is not possible:
- SPACE
- product1/adminguide
- product2/adminguide
Just simple stating that it is not possible because it breaks search is in my opinion a bad argument. It breaks search because search is not build right. If you display the parent page in the search results, it would fix the "problem".
So if i search for adminguide, i see these results:
- product1/adminguide
- product2/adminguide
And i get there with 1 search. So in stead of making something as complicated as nested spaces for a workaround for the above discussion when it can be easily achieved by improving your search engine (indexen the parent pages to make searches unique).
Thank you for the suggestion, Martin. But your company has not completed Atlassian's security self-assessment. This would be a blocker for me to recommend the SubSpace Navigation as a solution to any person experiencing this issue. Security is at the forefront of my thinking when looking at any solution:
- Where is the data stored?
- What metadata is created from this?
- Where is the code for the solution located?
- Who runs the code (3rd party, Atlassian or the user's browser)?
I trust Atlassian's Security Team. Beyond that, I have to have additional information to make any assessment.
The company I was working for at the time I filed the ticket (CustomWare) has gone on to become ServiceRocket (a pretty major Atlassian partner).
I started using Confluence when it came out because I was working at ThoughtWorks at the time, and (IIRC) the Atlassian office was in the same building as the ThoughtWorks office in Sydney and all those folks got along really well together.
I suspect this ticket is open to stop a bunch of duplicates from being filed 
Fun facts:
(1) When Aidan filed this ticket, Atlassian was two years old.
(2) Confluence was released in March 2004. So this ticket was one of the first EVER.
(3) I started using Confluence in 2008 or so. The company I worked for doesn't even exist any more.
(4) Atlassian rebuilt its entire cloud infrastructure in the time since this ticket was opened.
(5) HipChat was aquired, rewritten (stride) and abandoned since this ticket was opened.
(6) Answers.Atlassian.com was created since this ticket was opened, running on Confluence Questions (no longer a thing)...and moved to a 3rd party service as community.atlassian.com.
(7) Bamboo wasn't even in existence (released in 2007) when this ticket was opened.
There is absolutely no reason this ticket should still be open. :shrug:
Wow, this issue is still "GATHERING INTEREST" after being in existence since 14/Apr/2004
Yet the Confluence Server issue (https://jira.atlassian.com/browse/CONFSERVER-1095 is marked as NOT BEING CONSIDERED)
I am facing the same issue. Unable to have identically named child-pages for two very different parent pages. It forced me to change the name of the child-pages. Would be great if Atlassian can look into this issue quickly.
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
As a former Atlassian who lives down the street from the Austin office, I am more than willing to demonstrate how this problem affects my team if it will help gather information and get this fixed.
What is the current status of this ticket and when will we be able to create nested spaces?