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.

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

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.

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.

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.

Overview: Implement automated relationship creation between Lists and Tasks using formula-based lookups with support for flexible relationship mapping (one-to-many, many-to-one, many-to-many), eliminating the need for manual linking while maintaining data integrity through conditional logic. Feature Description: Automated XLOOKUP-style Relationship Engine with Dynamic Cardinality Users should be able to configure automated relationships between Lists/Tasks using formula conditions that: Automatically scan target Lists for matching data criteria Create relationships with configurable cardinality (1:1, 1:many, many:1, many:many) Maintain real-time synchronization as data changes Provide validation rules to ensure data quality and prevent relationship conflicts Relationship Schema Framework (Option to View Relationships in workspace) Schema Builder Visual Schema Designer: Drag-and-drop interface for creating relationship diagrams Entity Relationship Modeling: Define entities, attributes, and relationships graphically Schema Templates: Pre-built schemas for common business scenarios Schema Validation: Real-time validation of schema structure and constraints Schema Governance Version Control: Track schema changes with rollback capabilities Change Impact Analysis: Preview effects of schema modifications Schema Migration Tools: Automated data migration when schemas evolve Access Control: Role-based permissions for schema modification Core Functionality Formula-Based Lookup System XLOOKUP equivalent: =AUTOLINK(source_field, target_list, lookup_field, relationship_type, [match_type]) Conditional creation: Only establish relationships when specific criteria are satisfied Multi-field matching: Support complex conditions using AND/OR logic Dynamic updates: Automatically adjust relationships when source or target data changes Relationship Cardinality Support One-to-Many (1:M) Single parent record automatically links to multiple child records Example: One project automatically links to all tasks containing the project code Formula: =AUTOLINK(project_code, "Task List", project_reference, "one-to-many") Many-to-One (M:1) Multiple child records automatically link to a single parent record Example: Multiple invoices automatically link to one client based on client ID Formula: =AUTOLINK(client_id, "Client List", client_reference, "many-to-one") Many-to-Many (M:M) Multiple records can link to multiple other records bidirectionally Example: Team members linked to multiple projects, projects linked to multiple team members Formula: =AUTOLINK(skill_tags, "Project List", required_skills, "many-to-many", "contains") Use Cases by Relationship Type One-to-Many Examples: Department → Employees Project → Tasks/Subtasks Client → Multiple Contracts Product Category → Individual Products Many-to-One Examples: Multiple Orders → Single Customer Multiple Tasks → Project Manager Multiple Expenses → Cost Center Multiple Bug Reports → Software Version Many-to-Many Examples: Employees ↔ Projects (cross-functional teams) Tasks ↔ Tags (multiple categorization) Vendors ↔ Product Categories Skills ↔ Team Members Configuration Options Relationship cardinality: Select 1:1, 1:M, M:1, or M:M linking behavior Trigger conditions: Define when relationship creation should occur Validation rules: Set criteria that must be met before establishing links Conflict resolution: Handle scenarios where multiple matches exist or cardinality limits are exceeded Bulk processing: Process existing data when new automation rules are applied Relationship limits: Set maximum number of connections per record (for performance management) Advanced Features Cascading relationships: Support multi-level relationship chains Conditional unlinking: Automatically remove relationships when conditions no longer match Relationship weighting: Prioritize certain matches over others Batch optimization: Process multiple relationship updates efficiently Benefits Eliminates manual linking overhead across all relationship types Supports complex organizational structures and workflows Reduces human error in relationship management Maintains data consistency across Lists regardless of cardinality Enables scalable workflow automation for enterprise-level complexity Provides comprehensive audit trail for automated changes Flexible enough to handle evolving business relationship requirements

When a related task is displayed in a list column, it would be amazing to be able to open that task quickly. Instead the relationship modal opens up, and then the modal grows when all the suggested tasks are loaded. So to avoid mis-clicking I must wait for all of this to load and then I can click the task I want to open. If these related tasks could be opened quickly with a double click, that would be so helpful!!

I use ClickUp daily for task management, and I believe it would be extremely helpful to have a way to explore and visualize task relations in a network graph format. Specifically, I imagine a feature where tasks and their relationships are displayed visually as a network, allowing me to freely explore connections. A good reference for this idea is draw.io ’s “explore-view” ( https://www.drawio.com/blog/explore-diagrams ). For example, when working on a large project, many tasks are interconnected in complex ways. With the current list or Gantt chart views, it can be difficult to intuitively understand those relationships. If I could explore task relations graphically as a network, I would immediately see answers to questions like: “Which tasks does this depend on?” or “What broader impact does completing this task have?” This type of functionality would also be highly effective when discovering new related tasks or reorganizing existing links, ultimately improving efficiency for the entire team. Finally, I want to express my sincere appreciation for ClickUp. It has become an indispensable service for my work, providing an integrated experience from task management to documentation and communication. I deeply respect and thank the development team for their continued effort and innovation.