How Task Statuses Work

Updated

Task statuses in OnRamp give you an instant read on where work stands without anyone having to manually update anything.


The Four Task Statuses

Not Started

A task shows Not Started when none of its subtasks have been worked on yet.


In Progress

A task moves to In Progress when at least one subtask has been started but the overall task is not complete yet.


Finished

Answering a subtask moves its task to In Progress. When automatic completion from replies is turned on for your organization, a task can finish on its own. This happens when an answer through certain channels, such as an email or text reply, leaves no subtasks outstanding. Otherwise, someone marks the task complete.

Internal users with permission to update the project's tasks can mark a task complete, unless the task is Blocked. A Blocked task can't be completed until its dependencies are finished or removed.

Whether outstanding subtasks stop completion depends on the task's Require all subtasks answered before completion setting:

  • On: No one can complete the task in OnRamp until its outstanding subtasks are answered. Completing the task through the API skips this check.

  • Off: Internal users can still complete the task. Customer users in the portal can't complete it while subtasks are outstanding.

See -> Assign, Manage, and Complete Tasks in a project for more details


Blocked

A task shows Blocked when it depends on another task that has not been completed yet. Once resolved, the status updates automatically.


Tips

  • Some statuses are automatic. OnRamp sets Blocked from dependencies and moves a task to In Progress when a subtask is answered. You can also set Not Started, In Progress and Finished by hand, and reopen a finished task.

    • Blocked also comes from module work order restrictions, and a Blocked task can't be moved by hand.

    • A reopened task goes back to Blocked if its dependencies aren't met.

    • Setting a task back to Not Started also clears all its subtask answers.

  • If a task is stuck on Blocked, check its dependencies and the module's work order settings to find what is holding it up.

  • If a task won't move to Finished, check for outstanding subtasks and dependencies. When Require all subtasks answered before completion is on, OnRamp names the outstanding subtasks: Cannot complete task. Complete the following first: …. Otherwise, customer users see only a count of the subtasks left, such as Cannot complete task. 2 subtasks must be completed first. A Blocked task can't be completed and shows Task is blocked. When you bulk complete tasks, the dialog lists any tasks still waiting on unfinished tasks and won't let you confirm.

More in Tasks & Activities