A task is done when its done flag flips to true. The flag carries a completed_by (the user) and a completed_at (timestamp). Both feed Pi’s velocity model and the on-time launch report. Completing a task fires an onboarding.task_completed webhook and adds a task_completed entry to the audit log.
done flips immediately.You can also complete from your personal My tasks view in the Workbench, which is the faster path when you’re closing tasks across multiple onboardings.
Bulk completion respects subtask rules. Completing a parent task with open subtasks asks if you want to complete the subtasks too. Default is yes.
Within 30 days of completion, click the checkbox again or open the task and click Mark incomplete. The done flag flips to false, completed_at clears, and the audit log records task_reopened with your user and a timestamp.
After 30 days, the inline undo is hidden. Admins can reopen via Task menu > Reopen at any time.
The parent task auto-completes when every subtask is checked. The auto-completion writes task_completed with completed_by: system and auto: true in the audit log. Undoing the parent reopens it but leaves the subtasks done; you’d flip each subtask’s done flag back if you want to redo the work.
Closing every task in a phase doesn’t auto-advance the onboarding. Phase moves happen manually so you can decide carryover; see Move through phases. Pi flags a phase with zero open tasks as ready to advance on the Workbench.
completed_at uses the workspace time zone from Admin > Workspace settings > General, not the user’s local zone. Bulk completing across midnight can put tasks on different calendar days from what the user sees.done. Resume the onboarding first; see Onboarding states.Email help@pivotal.app with a screenshot of where you got stuck and the customer or onboarding id from the URL.