Multiple Closed Status
future
Log In
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)
C
Cherry-ann Keegan
Just wanted to second this, 6 years later. A closed status called Cancelled would be great, I want it gone from the main view, and also I want the team to be able to track the amount of jobs getting completed, cancelled or paused. So we get an idea if there's any patterns in the Cancelled jobs.
Luci N.
marked this post as
open
Hey, everyone! We've updated the status of this request to reflect its roadmap status. The Product Manager will provide updates on this post when they have new details to share! For more details about our statuses, check out this post!
David J Geiger
Luci N. Just for clarification, the status hasn't really changed, right? I clicked the link, the "Open" status appears to be the same thing as what "Considering" used to be.
Natalie Williams
David J Geiger that was my interpretation as well.
Luci N.
Hey, David J Geiger and Natalie Williams! Great question!
We've simplified the statuses and removed "Considering" since it was causing confusion!
The Product Manager will now move posts to the 'Future' or 'Planned' statuses once they are confirmed on our roadmap.
For this specific request, Caroline, the Product Manager, shared that this is on our radar but not yet committed to the roadmap. Because of this, we have moved it back to 'Open' since 'Considering' has been removed.
She also shared some more context in another comment below about the prioritization, if you'd like to check that out!
Happy Holidays!
N
Nicole Salow
PLEASE add this to the roadmap, it's such a basic feature from the user perspective that is really needed.
Christian Rigg
Caroline Ginty Looking through the roadmap, I was expecting to see requests with WAY higher votes than this.
.... How is it that this feature, with one thousand four hundred votes... Is being "Considered"... While there are features both planned AND completed in the roadmap with fewer than 50 votes??
What's the point of voting if our voices mean nothing to how ClickUp prioritizes requests. From what I've seen, this is one of the most requested features, and it's been that way for YEARS ... And then, dinky little features with 15 upvotes are getting prioritized?
Make it make sense. (Literally, though: Please explain to us how the voting process plays into the roadmap).
Caroline Ginty
Christian Rigg Appreciate your feedback on this, and I hear you on looking for more transparency. To give you a little peek behind the curtain, requests from the community are certainly a key part of our roadmap prioritization (for example, you can see that 3 of our top 4 all time Canny requests are currently in progress or in Beta), but there are other factors as well that play into our long term strategy. For instance, we need to take into account the individual capacities of each team, and of course, also allow us to also prioritize important overall quality and performance improvements within ClickUp.
We strive to be as transparent as possible with the community on what we are working on, and we do genuinely appreciate everyone who takes the time to vote and comment on Canny as it's absolutely something we look at regularly and weight heavily when doing roadmap prioritization. Thanks!
Load More
→