Add Columns/Filters in Everything View without adding custom field to the Workspace level
Ivan Villa
Custom fields can be set on:
Workspace level
Space level
Folder level
List level
When setting custom fields on WORKSPACE level, every task in every space will have this field. This could create noise for the spaces that do not need those fields, or need specific fields. So the custom fields are per space differently and some will overlap. So the Space level in great for that.
In the EVERYTHING view you can filter on a custom field to get insight on all tasks with that field. However, this is only possible with custom fields that are set on WORKSPACE level, so ALL spaces. If you select a SPACE level custom field it will convert it to a WORKSPACE level field and add it to all other spaces (tasks) as well. This is really bad. You now can't create everything views on that data you want and if you convert it to WORKSPACE you can not convert it back to SPACE as when deleting it in a space, it will delete it everywhere.
Log In
Caroline Ginty
Merged in a post:
Add filter on custom fields at the Space or Everything level without adding the custom field to that level
Jake Spirek
I have a custom field that I don't want to show on ALL tasks, but want a view at the Space or Everything level that shows me any tasks that have that custom field.
To be clear, I have just a few lists that need to use this field, so I
don't
want to add that custom field to the Space level because now it shows on ALL my tasks and it's a horrible experience to have too many unrelated custom fields show on every task.If there are any tasks with that custom field filled out, I want to be able to filter on that field at the space level.
Caroline Ginty
Merged in a post:
Custom fields on Everything should not be created on all the tasks
S
Sophie Guerin
Currently if we add custom fields on the views in Everything, all the tasks of the workspace will have those custom fields.
What would be nice is that Everything can get custom fields of all the lists/spaces BUT not the contrary. Example from a view in Everything, we see a task (Task A), from Space X, list L. If on list L we have custom field F1, then we can see F1 in the everything view BUT if we create a custom field F2 in the everything view, it does not get created in Space X. Maybe only on List L or Task A or not even.
Caroline Ginty
A
Alberto Alonso
This feature will be incredibly useful for people managing multiple projects. Right now I'm forced to use tags instead of custom fields to be able to filter at Space level all the tasks from different projects.
Caroline Ginty
Merged in a post:
Custom field column in views without adding the field to the location where the view is
S
Salah Boukadoum
You should be able to add a custom field column to a container (folder, space, Everything) without adding the field to everything in the container. In the UI you can show an empty spot or an icon indicating that the field is not in that task. This would enable management views where an element is set in the view across many tasks, even though the view displays some tasks that don't have that element. Without this, you can't efficiently manage tasks of different types in a view.
Guy Mannerings
This would indeed be useful, rather than having to add that Custom Field to all Lists.
Caroline Ginty
Merged in a post:
In space, filter by an List Custom Field
M
Marcio Lanser
I moved some space custom fields to a respective list, to these custom fields not view in another lists. But i can't filter when in a space view for these custom fields of a list. If would can filter by this, in "or" option, can create many relevant views, without have a space full of custom fieds that can distribute in each folder/list.
Now, it only can possible filter (in space) of the custom fields that be of space custom field.
Caroline Ginty
Thanks for the feedback Sophie Guerin! Would you expect then for it to not be possible to create Custom Fields at the Everything level, and therefore you could then show existing fields, but not create them there?
S
Sophie Guerin
Caroline Ginty: I dont need myself to create custom fields for all the tasks of my workspace, not sure if other users may need this or not. I am using Everything for views across the workspace, so I only need to view (not create).
Natalie Williams
Caroline Ginty yes I want to be able to view CFs at the Everything level without creating them there. Being given the option to create them would be fine. Currently there is no simple way (that I've found) to view tasks from multiple lists/spaces that use the same CF.
A use case: I have a date CF called 'Published' I want to see everything across all spaces by this date at once, but without creating a list and adding every task/subtask that has the field set it's not currently possible without adding the CF workspace wide. That's not what I want to do either as the field is completely irrelevant for the majority of my lists and would add unneccessary clutter.
Tyler Guthrie
100% yes! This issue has forced me to add field to a space level when really I just needed them on a list or two. I still wanted to filter by them at the space level. Now I'm in a pickle since I want to make some of the fields required, but they shouldn't be required on all lists in the space. Just 1 or 2.
Nicholas Estes
Merged in a post:
Everything View Filter on Custom Fields
Mark Verschuuren
Custom fields can be set on:
Workspace level
Space level
Folder level
List level
When setting custom fields on WORKSPACE level, every task in every space will have this field. This could create noise for the spaces that do not need those fields, or need specific fields. So the custom fields are per space differently and some will overlap. So the Space level in great for that.
In the EVERYTHING view you can filter on a custom field to get insight on all tasks with that field. However, this is only possible with custom fields that are set on WORKSPACE level, so ALL spaces. If you select a SPACE level custom field it will convert it to a WORKSPACE level field and add it to all other spaces (tasks) as well. This is really bad. You now can't create everything views on that data you want and if you convert it to WORKSPACE you can not convert it back to SPACE as when deleting it in a space, it will delete it everywhere.
Load More
→