Ability to set a status for lists and projects | Voters

Ability to set a status for lists and projects

Jill Bucher

I'd like to be able to exclude some lists or projects similarly to what I can do with the different statuses of tasks. Some of my projects are not yet relevant, so I don't want to see them during my day-to-day work.

One of my previous task manager tools had the ability to hide tasks of all levels from to-do.

September 30, 2018

Felix Plohberger

This would be useful to support project initiation and prioritization processes for PPM.

R C

Yes this is very useful, sometimes Lists that represent projects can go "on hold" and it would be good to have this Status, not just the current Color Scheme which is a little thin...

Rebecca Wilcox

I agree with this. In a project, we have lists for different time driven activities, eg. "Prep work" which once completed would be good to hide.

Sophia Kaminski

From support ticket: I'd like to create separate custom statuses for Lists

Maarten Tigchelaar

It's not only because of not yet relevant projects, but also for projects/lists with no open tasks (all finished). Now I see list/projects with no open tasks in the list view. Ok, I can archive projects with no open tasks, but I cannot archive lists.

To consider: When I finish the last open task in a list/project, ask me if I want to close the list/project as well.

Aaron Valverde

As already mentioned in this thread, I would also like to be able to set an active project to a status of 'HOLD' this would not change any In Progress data within the lists, its a project level status which removes it and all associated data from reporting and Active views. To view projects on HOLD, there would a project level filter for a Project Status.

Michael Ferullo

I agree with the ability to set a status for lists and projects. With our current design, we would like to be able to set a status for an entire project or list. For example, if we have a list named "Server Upgrade" which we are temporarily postponing, we would like some sort of ability to put this into an "On Hold" status and potentially hide it from our active list. We don't want to lose sight of it, but we also don't want to delete it from our list, especially if there have maybe been previous tasks already accomplished/assigned.

Another user (Mike Sawchuk) suggested creating another space and naming it queued projects, yet this comes along with creating an entirely new set of tags, permissions, etc. and is just too clunky of a solution for something that should be relatively simple for our team accomplish.

Mike Sawchuk

Michael Ferullo: 
If you just need to "store" the project for a while, it does work to just create a super simple space - don't worry about tags or custom fields, or any other setup, etc. in attempt to match the project you want to put on hold. This isn't required - and yes, it would be too clunky.
When you move the project or list into the space "queue" - some of those attributes will not be available for view while in this space, but if its just for temp storage, do you really need to view these details while it is on hold? When you restore the project to your "working" space, all the previous attributes like tags and custom fields that were assigned to the tasks and lists are restored automatically - it's just a display thing, that is all.
I takes me literally just a few clicks to create the super simple space (its a one-time event to create this for any and all queued projects) and move a project into it. 
I am not against the requested feature (I upvoted), but I do find the work around pretty simple and not requiring all that new space setup to match the specific project as you indicated. I just use one simple space called "queue" for all my queued projects - when I restore them to the working space they were created in, they are entirely set up as I initially had them. 
However, as Jill Bucher mentioned, if you regularly use the "all spaces" view my proposal doesn't really help except to identify it as queued - which could be done more easily by temporarily editing the name. More advanced filtering by space might be a handy feature as opposed to just one or all.

Muazam Rafique

It would be useful to label a project with a status, e.g. active, on-hold, closed (archived), etc.

it would also be useful to have a description/comments box at the project level. (I think this has been mentioned elsewhere). Recently a project that I was working on was put on-hold. I just wanted to record this fact, with a comment but couldn't do so. Ended up recording this information at the list level for that project.

Mike Sawchuk

Reply to Jill: While I do think projects might gain from having their own statuses, to do what you want with Clickup as is, you could simply create a new space and name it "Queued Projects" and put your "not-yet-relevant" project(s) in there.

If you need to begin the project at a specific time, create a task within called "Start Project", and give it a due date. When you receive the "Start Project" notification, you can just move the project into your working Space from the Queued Projects space.

Jill Bucher

Mike Sawchuk: Thanks Mike. It's worth considering, though I'm not sure if this will work the way I hope it will. Especially since I'm usually using the "all spaces" to get an overview over my projects. Since I don't think we can just have some of the spaces but not all selected, the tasks would still show up.

Mike Sawchuk

Jill Bucher: Hmmm ... sounds like a potential feature suggestion - ability to choose spaces to view rather than just one or all. I could see that being useful for other reasons as well.
But you raise a good point - if you regularly use the all spaces view it won't work quite like you want.
There has been a "snooze" feature suggested, where you can hid a task / project for x amount of time. I am sure the team is looking into the best way to kill as many birds with one stone, but the ability to hide (or minimize) items until either X time or X has occurred (maybe dependency driven) seems to be a popular request.