Ewerton Ribeiro
Problem:
Currently, users can mark tasks as complete even if important information in custom fields is missing. This creates process failures, especially in teams that rely on structured data (sales, operations, onboarding, etc.).
Proposed Solution:
Allow workspace admins to define certain custom fields as "required" before a task can be moved to a specific status (e.g., "Completed").
If the user tries to complete the task without filling the required field(s), a warning should appear preventing completion.
Example Use Case:
A sales manager requires that before a deal is marked as "Closed", the salesperson must select a value in a dropdown field (e.g., "Payment Method" or "Lead Source"). If not filled, the system blocks completion.
Impact:
  • Improves data quality
  • Prevents human error
  • Increases reliability of reports and automations
  • Helps enforce internal processes without manual checking