Required workflows: Status directions and approvals (conditional status changes)
Wes Brummette
[from support] If I have [statuses such as] open, requirements complete, in progress, development complete, closed can I set it up so that a task cannot move back from development complete to in progress?
Log In
Caroline Ginty
Merged in a post:
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.
Caroline Ginty
Merged in a post:
Block status change unless required fields are populated
D
David Greene
Please add native status transition validation. When a task is moved into a specific status, ClickUp should block the change if required Custom Fields are missing and show a prompt listing what’s missing.
Example: If moving to “Ready for Review”, require [Field A] and [Field B]. If either is blank, prevent the move and prompt the user to complete it.
Caroline Ginty
Merged in a post:
Validation Rules on standard and custom fields
Ryan MacAlmon (HPE)
Allow validation rules on both standard and custom fields. For example with Status equals In Progress, start date and due dates are required
Caroline Ginty
Merged in a post:
Custom role by List (status and fields permissions)
H
Henrique Rossato
It'd be great if we could create role permissions by List, in order to permit who can change from specific status to another one. Example: just the approvers role (for this list) can change to approved status or can change some fields.
Some complementary requests:
Daniel Urbano
Wes Brummette Juan Grandas Hi guys! Do you Know the status of this project?
Taras Kozak
In ideal world it could be an Advanced section in Statuses Modal to set all legal transition bi-directional graph (to excluse illegal arrows from all-to-all connection/direction) and required permission to do legal transition between statuses (who can change status for every arrow).
In this case you can block transition from "DEVELOPMENT" to "PRODUCTION" status skipping "TESTING" one.
Taras Kozak
In ideal world it could be an Advanced section in Statuses Modal to set all legal transition bi-directional graph (to excluse illegal arrows from all-to-all connection/direction) and required permission to do legal transition between statuses (who can change status for every arrow).
In this case you can block transition from "DEVELOPMENT" to "PRODUCTION" status skipping "TESTING" one.
R
Ronei Marques Martins Junior
Pleeeaaaaaase prioritize this!
R
Ronei Marques Martins Junior
Very much needed. I need to require some fields in certain steps of the process and this would be a great way to do it.
Evandro Araujo
How the heck this is not even prioritized yet?
Load More
→