[from support]: the ability for Folders and Lists to inherit views rather than having to setup the same view for multiple lists.
Actually, I originally suggested the same thing, but after working with 2.0 for a bit, I think the current design provides a level of flexibility that would be lost with inheritance. In the current design, space and folder views work with lists (when viewed from the space or folder level), yet can have their own view (when viewed from the list level). IMHO, I kind of think it will make things confusing to add inheritance at this point...
@布: The new features definitely help for list views. There still seems to be a gap for page views though. Currently, if I make a doc in a folder and want it to be accessible in each of the lists within I would need to do one of the following:
A. Copy the doc into each list. Any changes would need to be done in each place as well.
B. Leave the list I'm in to access the doc and go back and forth between the 2. This is tolerable if everyone has permissions to the whole folder. However, doesn't work for anyone that only has permissions on one of the lists in that folder.
I think the basic 'view' function should be 'inherited' and resemble the 1.0 functionality. The current implementation should be a 'clickapp' in my opinion as it adds quite some functionality and complexity in my opinion.
Just want to clarify. Are we talking about inheriting what I understand as a View's "Layout" in Clickup terminology? Or are we talking about what the Default View is for Folder and Lists?
This week, we're working on:
1) Views templates (save and load templates for views)
2) Default Space template for reach view (so you can use set a default way the views will appear)
We are still considering the actual inheritance feature and if it's entirely necessary. We'll revisit this after the above two points are addressed.
Keep us updated on any thoughts.
@Zeb: As things stand i really think that the Layout for Lists should be inherited by the from the Folder. If Clickup had the functionality to show different Columns for each List while viewing the entire Folder, it would make a lot more sense for the Lists to not inherit the Layout of the Folder, but unless that is a feature, it makes no sense for the Lists to have a different Layout at the List level then it does at the Folder level
@Kirk Mullis: You can have different columns/statuses for each List, and you can view them on the Folder level, is that what you mean?
@Zeb: i don't seem to be able to figure out how to show different Columns for different Lists in a Folder when viewing all the Lists in the Folder. The plus next to each lists header controls what columns are visible on all Lists in the Folder
@Kirk Mullis: Ah I thought you were referring to board view columns (ie. Statuses). I get what you're saying now.
@Zeb: The latest change works quite well. It provides a good balance between flexibility and standardization. I like it!!!
Please ADD THIS!!!!
For me, it would be helpful if created views and required view layouts can be inherited by children in the hierarchy. For example, views I save on the folder level can appear in every list in that folder. Views I save at the workplace (everything) level can show up everywhere in that workplace.
I can see this being implemented in a couple of ways.
1. Similar to how we can set use space statuses on a folder. We could have a setting to make parent views available.
2. We could have a view setting that allows children to inherit the view.
Either way we could set up the view once at the highest level needed and set the inheritance, instead of recreating it in each place.
@Dan Reynolds: I really like that ^^
@Dan Reynolds: This is EXACTLY how it should work - particularly for making lists at the Everything level - imagine making a list there and then freely navigating to other Spaces/Folders/Lists and maintaining that view
I think there should be favorite views so they could be applied to other folders/lists. From the required views page, you could have a dropdown (multi-select) of the views in the folder to be used as the starting point for each list's default.
We're thinking about the UI and UX for this now. If you have any ideas on how to do this, please let us know!
@Zeb: A couple suggestions...
If you're taking a 'snapshot' of the columns after they're set up and saving that as part of a list template, a 'column layout' checkbox would probably suffice.
If you're thinking of a 'views' perspective on this (per @John's comment), maybe adding 'Required views templates' to Spaces settings that are accessible across the workspace could work, but might be buried a bit too deep for the UX. Maybe using the + to choose task/page views and adding a dropdown similar to the Saved Filters dropdown would be cleaner.
This would be fantastic. Best if it could be set at the template level, but worst-case being able to set a default view (including columns and showing all statuses, including Closed) at the Space level would suffice.
Via a client chat:
Depending on how the backend structure works I think the most helpful thing would be a toggle to "freeze" a layout I've set.
Basically if I have that on then wherever I navigate to keeps the same columns, sorting, filtering, etc.
I'm not sure how that would interact to moving to a location with different custom fields though - it would probably be fine to just have any non-applicable fields disappear if you go to a place that doesn't have them.
Since custom fields can be set at the space level now, people can use that to keep the view consistent. I do wonder if they could be created at the workplace level eventually.
I'm not a web developer so I don't really know what's easier or harder to develop, but my intuition is that keeping the idea of every location having its own view data might be smoother than forcing the 1.0 function back in.