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
C
Claire Albrecht
Bumping this, with my comment from another post where the suggested fix is to create a workspace-wide 'Relationship' from the custom field manager:
I had the above question ready to post on Canny as it's not intuitive that the feature you've indicated exists—only stumbled across this today, and I'm still coming across a problem where, when creating a Workspace-wide 'relationship', it actually creates a Tasks field, and when I add a link on an A list to this field, it doesn't show up on the B list as a corresponding relationship task. Also, when going into the task through the B list, it shows the task from A list under 'References', not under 'Linked'.
This means that the workspace-wide Relationship isn't actually functioning as a Relationship. Is there a way to get an actual Workspace-wide or at least multi-list Relationship field?
P
Pavel Jarolimek
To use CU as CRM we need to relate tasks in different spaces to list containing "clients". We can do it through workspace relationships, but there are limited Roll ups newly called Relationship Columns, because "Only List to List Relationships support using Custom Fields as Relationship Columns." Therefore the CRM is quite limited. List to list is insufficient because we add "clients project tasks" in multiple lists/spaces (departments) and we need to be able to create relationships in multiple lists/spaces.
M
Miriam Daub
Among other relationship enhancements (referencing rollups in automations, grouping and filtering by the relationship value, etc.), this is very important to keep a clean hierarchy in ClickUp. You can't purport to be a 'CRM replacement' but then have lackluster relational functionality.
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.
M
Miriam Daub
Ryan MacAlmon and having to re-tag it each time! I have to create automations in Make (which don't always work) in order to automate re-tagging the relationship when the task moves from one list to another (which is our way to hand it between teams/major phases in our process).
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:
Load More
→