Required / Mandatory Fields to close a task, including Comments
J
John Jones
We have some good discussion right now around the new "required fields" feature. Thanks to ClickUp for this!
@Waleed created a new follow-on for Default Fields, not Custom Fields:
There is a lot of sentiment for the same when closing a task, so I wanted to create this request for that need as I didn't see it elsewhere in the Forum.
I would also like to have the ability to require a "comment" when closing a task. This helps with software engineering and brings the "resolution" feature of Jira, very popular, to ClickUp. When this is turned on, a window will pop up asking for a comment around "what happened to close the task." It's very similar to the "Incomplete Warning" message.
Log In
Caroline Ginty
Merged in a post:
Required fields on Close Status
B
Beth Swanson
It would be very helpful to be to require fields when the status of ticket is moved to close. Ie problem state and solution.
Caroline Ginty
Merged in a post:
Mandatory field for status change
Sam Jenkins
I've seen a couple feature requests for having a field mandatory on creation but I think it would be useful to have the ability to specify mandatory fields that need to be completed for a task to progress to the next status.
For example having a "PO Sent" status requiring the PO number to be provided or "Assigned to writer" requiring a writer field to be completed.
L
Laurel McIntire
Allowing a field to be mandatory in order for a task to progress should be like creating a dependency without requiring an additional task/subtask relationship.
There are times that my tasks have different stages in a flow that need to be met before progressing forward, but I don't want to have to create a subtask structure just to outline each "stage."
I'd much rather have a custom field that outlines the different stages and have requirements fulfilled before moving to the next stage.
Particularly because the parent task's fields don't rolldown into the subtask nor do the subtask's fields rollup into the parent task. I'd like to have them all live in the same place.
Jack
This would be super helpful for us, we're using ClickUp as a baby-ERP right now as our manufacturing isn't large enough to justify full-scale ERP implementation. We want to block the change of status of a task (task type: production order) until all required Custom Fields are filled (quantity, delivery date, etc.)
John Horwath
I agree, all your competitors have this functionality.
H
Henrique Rossato
I also created a new request complementing this...
H
Henrique Rossato
I also created a new request complementing this....
Brian Bakkebo
I totally agree here, this is very lacking.
We need the ability to enforce that estimated time is tracked on status changed. We could use this for other fields as well.
This could be added as an automation. It is what we are doing now, but we can only notify that the estimated time field must be filled it..
This is not good enough!!
I found 4 other tasks which are similar one which could be rolled up into 1 feature. There probably is more though.
Add requirements before status changes
Required / Mandatory Fields to close a task, including Comments
Required field based on status not only on creation
Link: https://feedback.clickup.com/feature-requests/p/required-field-based-on-status-not-only-on-creation
A bit broader:
Mandatory fields
I see currently that Wrike natively supports this and several other project management applications have work-arounds for this feature.
Andrew Untersee
Still need something like this in 2025
Belle Niba
Additional Scenarios:
- Allow required fields to be set at list, folder and space level.
- Allow required fields to be set by task type. For example, If a task type is "Bug", I'd like to make "Priority" Required. OR I could set it at the list level where all bugs live.
Load More
→