Multiple Closed Status
future
Log In
Caroline Ginty
Merged in a post:
I want to add multiple statuses in Closed
Ahmmed Madhurja
I want additional status field in the Closed status. For example, if I want to close a task I can rename but I want to have +Add status within Closed like other Task Statuses.
Brendan W
Merged in a post:
Allow multiple Closed statuses (e.g. Completed, Not Applicable, Cancelled)
Ricardo Gouveia
ClickUp enforces a single Closed status to represent all terminal outcomes.
This causes friction and incorrect data when closing parent tasks with subtasks that are not required or not applicable.
Currently:
A parent task cannot be Closed unless all subtasks are Closed
Subtasks marked as Not Required / Not Applicable still block parent closure
Users are forced to close subtasks as if work was completed, even when no work ever occurred
This creates semantic inaccuracies, especially in reporting, audits, and post‑project reviews.
D
Daniel Alexandre
I concur. There are many times I am asked to determine whether something is possible or not, and I would like to be able to close a task with "Cancelled" as well as "Complete", for example.
N
Nicole Salow
Still waiting on this one, would prefer it being worked on now as it's clearly needed, but at least it's 'future'.
Andrew Timmons
You specifically seem to be avoiding CRM related workflows, which is fine since you can customize things. But if you're going to ignore those features, this needs to be available.
Use Cases:
- In CRM workflows where Account/deal workflows and task workflows need to co-exist, you may need a closed/won status and a 'Complete' status.
- Dev Workflows - Complete/Deprecated/Cancelled/Not In Scope etc are all separate statuses where I both don't want to see them in my pipeline AND want to know the difference.
- In just basic project workflows Complete and Cancelled are two distinct closure statuses.
To close the loop - multiple done statuses meaning that the tasks still show up isn't a viable option for user friendliness and avoiding clutter. This is especially the case on large enterprise projects. Additionally, as ClickUp reporting is generally weak (not that I expect it to be exceptionally robust) we ship this data out to a cloud tenant where we can manage our own budgets and other info. Closed status differentiation in that case is vital.
Caroline Ginty
marked this post as
future
P
Peter Jansen
I don't think its that debatable as a feature. There is a million use cases where this makes sense. And if someone does want to stick with the default it is not getting in the way. No brainer for me...
N
Ned Smith
It would be great to just remove the 'done' status (It's really not useful for me) and let us add other completed status options...
Mike Lloyd
Agreed. There are multiple reasons why a task might be closed and the status can reflect that. We have a "Not planned" status which is done and just sits at the top of every list annoyingly.
K
Karen Tyrrell
Agree, it would be good to have the ability to set more than one Closed status type rather than just being able to add custom Done status, as if a task status is in the Done category it still appears on the counter beside the list in the side bar, the tasks remain in the view on the list as an active status type (rather than disappear unless 'show complete' is selected, and also clutters dashboards etc. For example I would like to have options for custom closed status of 'Not Applicable' so the task stays on the list as evidence that it was assessed but closed as not needed (rather than having to delete it)
Load More
→