Workflow status: define who can change a specific status | Voters

Workflow status: define who can change a specific status

João de Souza

I work in an industrial engineering designer. Here we prepare dozens of documents every day. For us, each task in a list in ClickUp is a document. Each document will pass through the hands of at least 3 people: the creator, the verifier and the issuer (who sends the document to the client). It would be really nice if I could lock the statuses as follows: only the developer can move the task from status "to do" to "in verification", only the developer can move from status "in verification" to "ready to send" or "not ready for sending" (returning the activity to the creator), and at the end, when the document is ready, only the sender can move the status from "ready for sending" to "sent". Please help me with this, it's something that already exists in other applications and would be very useful for us here at the company.

August 16, 2023

Simon Stender

This would be amazing to have. Often it doesn't make sense that some people can move tasks to certain statuses and it is very likely an error that causes issues to get lost or miss-categoriesed.

In Software Development, a new QA-Tester could mistakenly change the status of his task to Done (because he is done testing) but skip the Deploy step. Then the ticket is lost until someone starts searching. So it would make sense when only a Developer with Deploy access can move tasks out of this step.

Alex1

yes please, the admin must check work of users and can be able to select status "CLOSED STATUS"
and the users can be able to select only status "DONE STATUSES"
because admin will check work of users

Cynthia

We need this too. Hope this can be worked on soon

Andrey Bychkov

We need this feature too.

Anurag Jayaraman

Upvoting this. My org uses Clickup for managing sprint tasks progress, and often there is a need for product documentation to be attached before a task can be closed. If I am able to set who can move a task to a "Done" or "Complete" status, that will help with ensuring delivery compliance for the product team.

Chantal Arneaud

Definitely need this feature for status and for documents

Michał Piórkowski

It would be great feature! I thought about dividing process into different lists to give different permissions. But your idea is much better.

Clive Townsend

Same thing for Priority!

Megan Miles

I do like this. I think at a minimum, it could be useful to limit the final step to just the "sender" in this scenario, and they'd be responsible for confirming (via comments?) the previous steps were completed correctly. Either way, locking it to just one user/role having the ability to close would be great. Keeps things from getting lost!

Stian Henriksen

Yes please - Our scenario is simpler, but controlling which status specific roles can use would solve the issue where a user accidentally closes a task rather than completing it (which causes some problems with billing). It would also prevent users from re-opening a closed task. Make it happen people!

→