Allow custom Relationship fields to be defined at the workspace, space or folder level
Asher Treby
I was really excited to try out the Relationship custom field because I have been using the Task custom field to effectively create a look-up field. The best bit about the Relationship custom field is the ability to say which list contains valid tasks for the custom field. One example for us is a Clients list, that is then the lookup list for a Client custom field.
However, to make this feature really usable for us we'd need to be able to define a Relationship custom field at the workspace, space or folder level.
Log In
Ryan MacAlmon
Caroline Ginty-
When creating the relationship field at the different levels we need to have the ability to select from a single list.
Today this is not possible. You can only do this from the list level. The workaround is to create the field x number of times per list.
Caroline Ginty
Merged in a post:
Relationships should be like other custom fields, assigned at any container level
S
Salah Boukadoum
We use global lists of items such as "related organization" and "related topic" to be able to link together tasks from throughout the workspace that are related to a particular organization, topic, person, etc. But for this we have to add a "related organization" field to every list, and then the related organization item itself has 100 entries in it. Please make the relationship custom field type work like other fields that can live at any level in the heirarchy.
Caroline Ginty
Merged in a post:
Create space-level task relationship custom fields.
Wesley Rodrigues
Create custom relationship fields to make it easier to link tasks to the client or project. The idea is to have a relationship field in view so that we can always remember to refer a task to a client and thus be able to view all the demands related to a client or project.
This applies when a client is managed in a folder or space different from the folder or space of the task to be performed.
J
Jeff MacNeill
If this is referring to custom rollup fields within a relationship then, yes please this would be sooo helpful. If a Custom Field is defined at the Space level you should be able to add a rollup of that custom field in the relationship at a Space level. Currently you can only add roll up fields for the basics -- dates, creators etc. At a List level you can do Custom Field rollups - but not at a Space. See attached image for Space rollups (left) List rollups (right) these fields are all defined at a space level.
A
Alberto Alonso
Probably related with this other one:
A
Alberto Alonso
Totally agree with this. The fact that the relationship custom field cannot be used across multiple locations is a bummer, given that if properly implemented it would unleash a lot of ClickUp potential.
A
Alberto Alonso
Probably shall be merged with this one:
A
Alberto Alonso
Agree this is indeed very much needed. Right now task relationship (from an specific list) custom fields cannot be used across multiple folders and/or spaces.
Benjamin van Arendonk
This feature would allow for a far more robust CRM-like system, currently I am looking into connecting Client data (phone number, email, etc) to relevant tasks that involve that client, but to do so I need finicky workarounds that only half work.
If I could simply connect one Space (the task space) to another space (the client data space) and search for tasks from one to the other with the relationship custom field at the space level, this would be perfect.
Wesley Rodrigues
One suggested use that I see is very necessary is the creation of custom relationship fields to facilitate linking tasks to the client or project. The idea is to have a relationship field in view so that we can always remember to refer a task to a client and thus be able to view all the demands related to a client or project.
This applies when a client is managed in a folder or space different from the folder or space of the task to be performed.
Load More
→