Relationships between task types
Ivan Villa
Problem:
We use custom relationships to link different types of work together, such as relating features to sprints. However, our organization is currently facing limitations because these tasks types are spread across different lists and the current implementation of custom relationships restricts a single list to only one relationship.
Ask:
- Enable the ability to create relationships between the task types themselves.
- This would allow "features" to be related to "sprints" and it would function seamlessly across the entire workspace.
Log In
David Haddad
This is beyond huge and would transform ClickUp in one single act to be much closer to a true "all-in-one" app. Here are my thoughts on how this would work at a basic level. Currently relationships can be created between lists. So that I could have a list titled "support tickets" that can be related back to a list titled "accounts". The big problem here is that I might want to create a "support ticket" in any number of different spaces/folders/lists.
With relationships between task types this would become easy. For instance I could create a relationship between the task type of "account" and "support ticket". Now it no longer matters where an account or support ticket resides.
This is what is needed if CU is ever to able to
truly
become a 'CRM' or 'ticket software' etc. on a deeper level. It would solve so many issues...Thanks!Leo Bastian
YES, plan it on the roadmap asap please! :) Subtasks of subtasks of subtasks seems to be currently the status quo to work with clickup and creating and maintaining custom relationships is a hassle without value (e.g. not even displayed in gant - was trying to find a workaround for relationship overview), thus the overhead is not really worth it at the moment - This would definitely help and be a good first step!
Matthew Burt
If I'm understanding this correctly, this would allow relationships between CTTs WITHOUT the need for List custom relationships. To further this idea, it appears what you're describing would allow for a newly created CTT task to have Custom Relationship Fields built into it that relate it to other CTTs and allow for the creation of new Related CTTs directly from the primary CTT. I assume you'd implement this by having each CTT have its own locked/walled-off list that is specifically for that CTT and all newly created tasks with that type would go on that specific protected CTT list.
This feature request sounds like something I want/need but the wording is a bit confusing how this would actually work.
David Haddad
Matthew Burt: "If I'm understanding this correctly, this would allow relationships between CTTs WITHOUT the need for List custom relationships."
This is exactly how I hope it will function, it would be 100x as powerful as relationships between lists.
John
It would also be great to limit relationships (i.e. an opportunity can only be tied to one account, but the account can have multiple opportunities).