Feature Requests

Please search first before posting to help others find and vote for your idea!
Updates to Relationship custom fields: shared across lists, Related tab navigation, and Related tab filter
We are utilizing custom field relationships to associate all work across spaces and teams with our clients. Example: Client A has 3 projects in Implementation, 7 issues in Support, and 3 items in Engineering/Development that are all visible in Client A's record(task). We currently have 72 relationship custom fields, and the number keeps growing. We are running into some issues navigating these and have concerns with maintaining these relationships. We would like to request the following items be considered: The use of the same relationship field across lists. We would like to build a single client relationship field that can be added to multiple spaces and lists to connect items back to the client's record instead of having to create unique relationship fields for each list. This would reduce the number of duplicate 'client' fields. Currently, task cards display all relationships at a glance. When you click on one relationship type, it opens the Related tab. It would be better if when you clicked on the relationship, it not only opened the related tab, but also went directly to the corresponding section in the related tab. For example, if I click on the 25 Client Contacts link under Relationships, it would open to the Client Contacts section on the Related Tab regardless of its relationship order. This would help us tremendously as it eliminates our need to scroll through a large amount of empty sections in the Related Tab to locate the existing relationship. Better yet, if we could have the ability to filter the Related Tab in tasks down to only those sections where a relationship exists, we could more easily navigate our relationships.
1
·
Relationships
Relationship fields cannot be restricted by Task Type ("This field is currently not supported by task type")
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!
1
·
Relationships
Faster task linking in List view + project-scoped bidirectional links
Hi ClickUp team! I run an indie game studio and use ClickUp to map interconnected game systems and entities, not just track production tasks. Task relationships are genuinely useful for this, but creating and managing them gets cumbersome as the map grows across multiple projects. Two improvements would make a big difference: Link visible tasks by clicking them in List view Currently, creating a relationship or dependency requires opening a menu, searching for a task by name, and checking that it’s the right one, even when both tasks are already visible next to each other. I’d love a “connect mode”: * Choose “Link task,” “Blocks,” or “Blocked by” on task A. * Click task B directly in the list to create the connection. * Support subtasks as both the source and target. * Show the dependency direction clearly before creating it, with an undo option afterward. Gantt already supports drawing dependencies between tasks. A similar interaction in List view would let us build connections without switching views or assigning dates just to use a visual linking workflow. Scope standard bidirectional task links to a project Different projects often contain tasks with identical names, such as “Building system.” Searching across the entire Workspace makes it easy to accidentally link an entity from the wrong project. Please add an option to restrict standard Linked task selection to the current List, Folder, or Space, while preserving automatic bidirectional linking. Custom Relationships scoped to a specific List don’t meet this need because I need the connection reflected on both tasks automatically, without manually maintaining two separate relationships. These improvements address two separate problems: repeated searching slows down linking, and Workspace-wide selection increases the risk of incorrect connections. Together, they would make ClickUp much more practical for managing large, interconnected project structures. Thanks!
0
·
Relationships
Load More
→