Group by Status 'Type' (Not started, active, etc)
Ardent Growth
Reviving this post: https://clickup.canny.io/feature-requests/p/group-by-status-groups-types
We too have different status for different lists. We use Kanban and each status is the stage of the workflow but we'd like to aggregate these up to calculate flow metrics at the folder and space level by having the ability to GROUP BY Not Started, Started, Done, Closed instead of the granular statuses within each.
Log In
Caroline Ginty
Merged in a post:
Choice to group statuses together to show them when many different statuses are shown
Y
Yoyo Xiao
Such as grouping all the "closed" statuses and "Active" status as the statuses can be different across lists, so viewing things by status in "everything" does not give a full representation
R
Rebecca Julius
I was just looking for a feature like this to exist. I am using a list to show how "complete" certain groups of tasks are and I really don't need the breakdown of specific steps, I just want to see "not started", "in progress" and "done" but each of those has multiple steps muddying up the waters here. Thanks!
Skyler Reeves
With the upcoming Group By Task Type coming, these seems like a wonderful time to remember this request as well. Us Kanban adherents would greatly appreciate it. 🙏
Brenda Perkinson
This group by would be great! Like Ardent said, especially for aggregate metrics and dashboards!!
Christo
I like this! I hack my workflows by using custom dropdown lists for workflow steps, so that any status reports or dashboards at a workspace level is very simple. That does make it harder to manage workflows with teams and clients though, as there are TWO things to update, not just one.
Caroline Ginty
Thanks for the feedback, Ardent Growth! The use case definitely makes sense!
Ardent Growth
Caroline Ginty: It would also make the Everything View about 42 times more powerful. 😎
Thomas Kirven
Caroline Ginty: this is great! Along these same lines, I'd love to see a Status Group for "Buffer" or work that is neither Not Started, In Progress, Done, or Closed. This "buffer" status is essential to proper kanban flows — not everything stays in progress, sometimes it's waiting on external dependencies, which should be treated differently. What are your thoughts on how to frame this use case effectively?