Feature Requests

Here's a sample use case: I want to create a list of projects and group them by Client. The Client is a relationship to a task in a list called Clients. For some reason, I do have the ability to group by some of the linked items, like assignee (in this case I called it "Client Owner").

Dashboards currently don’t support rollup, formula, or relationship fields, which prevents accurate reporting on client lifetime value, project profitability, and cash flow. Enabling these fields in all dashboard widgets (calculations, charts, task lists) would eliminate workarounds, ensure data accuracy, and unlock true CRM-level reporting inside ClickUp.

[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.

It would be useful to be able to Link a Task to a List, Folder or Space. This would be useful for linking Tasks to projects outside of the list it lives in.

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.

This was noted in the "Recurring Relationships" feature request as not being a part of scope of the solution—but this isn't a solution at all. As noted there, all of my use cases for relationships use the "specific list" scope limiter and I'd surmise this is true for at least 90% of everyone else's use cases.

Currently, if you have a relationship created by using the option 'task from a specific List', this relationship will disappear if you move the task to another List or duplicate the task. Allow these List to List relationships to be maintained when the task is moved or duplicated.

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).

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.