Prevent Task from Being Marked as Complete If Required Fields on Custom Form Attached to the Task Are Blank

Thank you for the submission! We think this is a good enhancement to the Workfront platform overall and this product area in particular!

Workfront currently prioritizes large-scale, foundational enhancements such as the new Reporting experience and changes to the core data model, so this item does not fit in our near-term roadmap. As such, I am marking this as Declined now, but we'll keep this in our backlog for the improvements for this area so that we can revisit the decision in the future.

We have to use fusion to create workarounds, please implement this feature.

This functionality would be a win for our teams, too. It's not exactly a "required" field if a user can close the task without filling out said field!

We've had to configure Fusion scenarios and approval tasks in order to ensure users are completing mandatory fields within custom forms and tasks before being able to close it - it does seem to be strange behaviour that mandatory fields need to be policed this way! It would really help to simplify our configuration if an enhancement could be made to the product to fix this.

This is something that is crucial to our users and agree is a basic requirement. Could we escalate this? As said above, this was raised in 2017!

It seems like lots of users want this enhancement, I really believe Adobe should put this one to the top of the list for the next release.
This post/idea was raised back in 2017, it's now 2022 and you still can't make required fields mandatory until a user clicks into a custom form, which isn't a great system design. You can close a task with fields uncompleted and there is no error message or anything telling the user that there is something they need to fill in.
We want this escalated as it is causing us a lot of issues regarding the transferring of data and ensuring users are filling in all the required information.
Thanks

We were just testing the required fields in a task and was shocked to see I could close the task without filling in the Required fields. This is basic level requirements and should be restricting the closure of the tasks, otherwise what is the point in allowing 'Required' fields to be added at Task level. This needs to be added ASAP

We were just testing the required fields in a task and was shocked to see I could close the task without filling in the Required fields. This is basic level requirements and should be restricting the closure of the tasks, otherwise what is the point in allowing 'Required' fields to be added at Task level. This needs to be added ASAP

We were just testing the required fields in a task and was shocked to see I could close the task without filling in the Required fields. This is basic level requirements and should be restricting the closure of the tasks, otherwise what is the point in allowing 'Required' fields to be added at Task level. This needs to be added ASAP

This should be basic behaviour. What's the point of providing a 'required field' feature when colleagues can either ignore it or not even be aware they need to complete these fields if they don't edit the form to fill them in? I'm rather dumbfounded that this isn't basic functionality.