Absolutely needed! I do this all the time.

Absolutely agree with this thread. Being able to mention lists, and have them show up in various views is crucial for the way we organize our projects. I would love to see Clickup offer this eventually! Thank you

In terms of referencing, would love to be able to reference folder and list names so that you can create automations to populate custom fields. E.g. if I need a list to populate with the name of the client & project (folder & list titles) in columns when I create a new task then I wouldn't have to manually enter each time!

Agree, would like to see Lists have the same visibility across ClickUp as tasks - @mentioning, status, etc.

I'd like to clarify that a huge feature I am waiting for is the ability to @mention the full range of entities in ClickUp:

As Docs have evolved, you guys have quickly added the ability to @mention them around ClickUp. I am constantly in need though to mention my lists. They are projects or "features" or other big pieces of my system, and would be very useful to talk about in Comments, etc. So I'd like to request that first in line of items to get the @mention capability would be lists!

Thanks guys!

This will be the logical result from an expected improvement in Clickup that tasks become entities which are independent of any project or container. The fact that they may show up in a project is because of their relationship TYPE which says something like 'is part of project'. But another relationship field type could be 'is related to' or any other type you can think of. Its up to the user to create and these relationship types but of course out of the box the most obvious ones would be in place already.

Within a 'Project template' one of the custom settings could be that the project container has one or more 'views' which list by default entities which reference the project in some way. An obvious example could be a default view based on the relationship type 'is part of project'. This relationship type very likely can have implications on the permissions of the entities that have this relatinship, such as read and write permissions to users that are part of the project.

The scenario mentioned above is my expectation of Clickup and an example of how to solve a problem by thinking ahead in the structural development of the platform. This prevents the common mistake that a system becomes a scrapbook and patchwork of not cooperating solutions.

@zeb-1 Is there a possibility that a way round this will be in early versions of ClickUp 2.0? Would sort out my issue of having a calendar side panel full of unscheduled tasks that aren’t really tasks 😀. If we could maybe just define a list as not being an actionable list that would be a boon. Thanks.

Thanks Zeb. Probably the most thoughtful, open and reactive company I’ve ever come across :). On current performance deserves to succeed BIG time. Make sure you keep that approach please - so many small startups lose it after the initial enthusiasm phase - not to mention any names!