Project Statuses and Automation
Impact of status changes on Tasks, dates, and notifications.
Last updated 20 days ago
The project status indicates its stage in the process. Status names, colors, and the order in which they appear are defined by the administrator, so the list in your system may differ from the examples.
You can change the status via the form, the card view, or the Kanban board. A status change can record the project completion date, notify team members, send an email to the client, create tasks from templates, or mark existing tasks as complete. Review any additional options displayed on the form before confirming the change.
Mark completed work with a "Completed" status rather than deleting the project. This preserves tasks, time logs, files, and financial history. A "Cancelled" status is appropriate for work that will not proceed.
If new tasks are generated after a status change, check the task templates assigned to project statuses. If a client or team member received an email unexpectedly, the administrator should review the status settings and email automation rules.
Safe Status Changes
Before changing the status, review any incomplete tasks, active timers, and project members. If the form offers additional options, do not select them automatically: the completion of Tasks and the client notification are separate outcomes.
After the change, refresh the record and verify the end date, the new Tasks, the activity log, and the notification recipients. Reverting an incorrect status will not necessarily undo previous automated actions.