Feature Requests

[From Blue Whale] I would like to be able to add relationships in bulk, especially by adding a folder or list. This would particularly be useful for dependencies.

It doesn't seem there is a way to add the values for a rollup field. It would be great to be able to use rollup field values from relationships in formula fields.

Hi, ClickUp is in the right way, but it lacks of something very usefull: DATABASES, as in Notion. In fact that's the one of the most powerfull options of Notion. You can see it as a list of tasks (rows/records) with fields (columns). Then you can create new lists/tables/databases based on that data, related to that data, filtered by fields/columns... Once you have worked with databases, you know the very necessity of it. Regards

Consider the following situation: There are 3 Lists A, B, C each with a column called "client name" There is another List D which has a list of 1000 client names. I created a relationship field such that the column "client name" in Lists A-C can access client names in List D. However, since this relationship is on a list to list level, the information is lost incase a task is moved between List A-C. Is there a solution to this? Is there a way to create a relationship, such that the "client name" value is not lost when we move the request from one list to another?

It would be great to be able to give custom fields for a relationship in a task. For example we add a crm task and we want to see the email custom field of that crm task without clicking into it and search for that field in an other tab.

Many of our major projects appear as spaces or folders, not tasks. Being able to connect a doc to an overarching project instead of a task would be useful.

It would be so effective to have a relationship field be able to link 2-way. This would allow a seamless relationship between two tasks under the same relationship type. Right now, we can add the same relationship custom field into two different locations, however, when adding a relationship, from one task into another, where you add the relationship will sit in that custom relationship field, but in the linked task, it'll show as "Reference". If the same custom field relationship is in each list, and two tasks are added with a relationship together, my thoughts are we should have the ability to show it as a two-way relationship. Organizationally, this would be exceptional.

Currently, when creating a custom relationships, it is only possible to link a task to another using the relationship from one of the tasks. It would be great if you enabled the ability to create relationships which work similarly to dependencies. In dependencies, the relationship name indicates how each task relates to the other (blocking or waiting on), and the same should apply to custom relationships. So if there is a task that represents a customer, and a relationship that represents that the task is for that customer, than it should be possible to create the relationship both from the task related to the customer and from the task representing the customer itself. Each direction will have its own name. In our example it will be something like "Related Customer" and "Reelated Tasks". I do not see much use for custom relationships without this feature, as the current state does not capture any aspect of the nature of relationships (one aspect is relationships being bidirectional).

I would like to be able to link multiple lists in the relationship field similar to the way Goals allow you to select an entire list or multiple lists to a target. If a create a task, I'd like to be able to link multiple lists so that I can see the list names in the relationship field so I can click on them and be taken straight to the list that is linked to the task.

Relationships nowadays just allow to select tasks previously created. It would be nice if we coud add a new task directly on related list through Relationships.