Feature Requests

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 team, We're restructuring a List (Event Production) using custom Task Types to model a parent/child task hierarchy: a mother task type ("Evento") with several daughter and granddaughter task types (e.g. "Equipamento", "Nome Fornecedor", "Financeiro"), each with its own set of Task Type Fields, so that only the fields relevant to that type of subtask show up on it. This works well for standard field types (dropdown, text, number, checkbox, etc.) — we can lock a field to appear only on a specific Task Type. The problem: we also have a Relationship field ("Fornecedor Relacionado", type Relationship/tasks) that we need to lock to a single Task Type ("Equipamento") the same way, so it only shows up on that specific subtask type and not on every task in the list. When we try to add it under Task Type Fields, ClickUp shows: "This field is currently not supported by task type." and the "Add" option is greyed out. What we need: the ability to restrict a Relationship field (and ideally Formula fields too, since we expect the same limitation there) to a specific Task Type, exactly like we can already do with dropdown/text/number/checkbox fields. Is this a known limitation? Is there a workaround, or is this on the roadmap to support? Any guidance would help us finish this reorg without exposing Relationship/Formula fields across every task in the list. Thanks!

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

In ClickUp 3.0, I was able to show/hide custom fields in the Relationships feature. This allowed me to quickly view specific custom field values through the Relationships feature, without needing to open the task. Now, in ClickUp 4.0, this feature has disappeared. I can only show/hide the task’s native fields, such as status, creation date, due date, priority, assignee, task type, and a few others. All custom fields created by the user in the respective list no longer appear in the Relationships feature. It would be excellent to be able to show/hide custom fields in Relationships again.

Filtering and sorting are currently only available in ClickUp Views. However, when multiple tasks are connected through a Relationship field, there is no way to filter or sort the related tasks directly inside the task. The only workaround is to create a separate View and filter it using the Relationship field. This defeats much of the purpose of displaying a related list of tasks inside the task record in the first place. Please add the ability to filter and sort related tasks directly within the Relationship field. This would make it much easier to work with large numbers of connected tasks without having to leave the task and create a separate View.

The problem: List-to-List Custom Relationships (the only type that supports rollup fields showing Custom Fields from linked tasks) can only be created at the individual list level. There's no way to define a relationship at Space or Folder level that says: "every list in this location has a relationship with [target list]." New lists created in that location don't inherit it either. This means: - Every new list requires the same manual relationship setup, repeated identically each time. - Rollup fields (e.g. showing a "Next Action" field from a linked task) must also be manually added per list - Automations cannot create Custom Relationships or rollup fields, so the "Create List" automation action can't include this config - Super Agents / AI tools have no access to create relationships or rollups either, so even an agentic workflow can't handle this step What should exist: Space/Folder-level List-to-List Relationships: define once that "every list in this Space/Folder has a relationship with [defined list]." Any new list created (manually, via automation, or by an Agent) would automatically inherit that relationship. Inherited rollup fields: rollup columns configured at Space/Folder level should cascade to new lists, the same way Custom Fields do. AI/Automation access: creating Custom Relationships and rollup fields should be available as automation actions and as Super Agent tools, so these can be included in automated project setup workflows. Use case: A CRM with client tasks links to a Projects space where each client gets their own project list. Being able to see a field like "Next Action" from the linked client task directly on project tasks (via rollup) is extremely useful, but the per-list manual setup makes it impractical to maintain, especially when new lists are created frequently via automation. The logic is simple: "every list in this space relates to this other list." The current implementation just doesn't support that level.

I have a list where each task has a rollup. I need to see the sum at the bottom.

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.

I have a main task that contains relationships to other tasks, and need to hide any tasks that are closed so they don't appear in the relationship view. I don't want to have to unlink each task once it's completed, just so that it doesn't continue to show up on the main task.

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.