Got this notification in mail just today and beta sign-up is already closed. :( [I see this thread is from 8/19, so my mail was late, I guess.] My org needs this badly. Our space has so many empty parent pages that'd be better served by folders.
So is ordering of folders also the same as pages? I mean rights wise?
It is very annoying that page order rights are coupled to the delete and edit rights. Right now anyone can order the pages an move them, I assume someone can also move an entire folder?
I like having the option of both parent pages and folders. Folders are great for simple organization is desired and a narrative description at the parent level is not required. We have use cases for both styles.
Allowing duplicate folder names would actually make me use the feature. I commonly want a similar folder structure for multiple things without having to create separate spaces. This would finally bring me over to Team Folder.
edit: I just realized I made basically the same comment on a similar discussion in the private beta group here:
@Scott Beeson _CIS_@Stefan Tichelaar I just tested creating folders with the same name in the same space and you cannot. The behavior is the same as page names.
@Michael.C.Weihrauh Thank you for testing. To bad this limitation is there. I hoped this would finally solve issues we have with parts in the tree that should have the same name in different parts f the outline.
So folders are like pages, but with editor and view removed - but you decided to implement them as a different object type with slightly different behavior / api visibility, so it's easier for them to break add-ons? Yikes. That said, can i convert a folder into a page? If not, can folders be disabled per space?
What I like about parent pages is that our staff can include a summary of what that section covers, giving us a clear understanding of all the child pages. Folders don't offer a way to specify the contents of the child pages. While this might not be important to some, it's always good to know what the child pages are.
There's some cases in wich you would like to display some instructions or intro for the sub-pages. However in some other cases, you only would like to group the contents with no previous information. The beauty of this feature is that now you would be able to choose what and when to show intro or when group this info.
I noticed a couple of issues/unexpected behaviour with this addition, both issues seen as a result of copying the link to a folder:
When following the link in a browser it displays the first page within the folder, it makes sense that this is the case but this is not documented in Atlassian - use-folders-to-organize-your-work
Additionally, when adding a confluence link to a Jira ticket the URL resolves to the space `Home Page`, which is sort of annoying.
I doubt I will use folders much, as others have commented, parent page separators are useful for describing the child pages.
> This is precisely why we are still allowing users to create parent pages
If you take away parent pages, and only have folders, you will be replaced by Google Drive.
I have no idea why you added folders at all. You could have fixed one of the billion bugs instead of adding a feature that literally degrades your product to something we can get for free from a superior supplier.
The business logic division at Atlassian must be literally insane.
I would actually much rather see a Folder feature work as a namespace, so that all the pages below it could have the same names as the pages in different folders.
@ultstein: That would be the first thing that would get my support for folders. Some way to have duplicate page names within a space is sorely needed. I'm tired of creating new spaces for basically everything.
You are spot on. Not to belabor it, but I hate having to have a page structure like
Some Crazy Project
Some Crazy Project Minutes
Some Crazy Project Notes
That is my current layout. With your proposal I could do
It seems like this feature breaks the Content tree. I mean, my space suddenly says there is no content,
but if I change the Content filter to another content view (one that does not rely on folders feature), all the pages are shown, including the archived empty pages that I changed to folders:
So, all the folder-ing becomes useless.
EDIT: Nah, disregard the comment. It just happens to enforce something a bit more strict.
If you set the landing page for your space to something different from the root page, it won't work.
If you happen to have more than one root-level page, it won't work either.
Once you correct these, things reappear in your Tree view:
I'm liking this new option, however I have noticed one issue already: When linking a Confluence Space to a Jira Work Management project, it will NOT show any folders in that space in the nav menu.
47 comments