One option I have used in the past (hi Jira !) for this is to have a separate field for Resolution - Fixed, Not a Bug, Cancelled, etc.

My guess why this is not even being worked on after so long is most likely this is one of those crazily tedious to implement feature despite it being seemingly simple. Maybe cause the "Complete" status is hardcoded, and that development decision has come to bite ClickUp down the road, so now trying to abstract the "Complete" status is full of friction.

BUT at the same time, this affects so many workflows..... And is causing us friction also.

This needs to happen for many reasons, which have already been mentioned. It's a basic need, especially when tasks can be shared between lists where statuses might need to differ slightly.

In a few months, we are having hondred of Clickup users, but we are missing this feature to create multiple "closed" statusses. We are in need of a Cancelled status with the same functionalities as "complete"... Meaning that the tasks are not shown anymore by default.

Fe;

So frustrating to have this fundamental issue not even acknowledged. It stays a daily frustration to see cancelled tasks count as open, show when users expect completed (in reality, only closed) tasks are filtered out--including on dashboards--prompt users that not all subtasks/dependencies have been addressed (again, requires them to be /closed/), etc.

We really appreciate having the distinction between "done" and "closed", but as-is it just doesn't work for us when we have to put our other closed options like cancelled, expired, denied, etc. as done.

Cancelled, PLEASE! :)

All those years and no return from something so important.

I need Cancelled

Yep!