Task statuses in ClickUp (Workflow)
ClickUp statuses act as labels that show where a task is in the workflow, such as To Do, In Progress, or Complete.
These statuses help ensure smooth coordination between our team and yours by making it easy to see what’s currently being worked on, what’s under review, and what’s been delivered.
Our status workflow is outlined below to help you understand:
- What each status means
- How tasks typically move through the workflow
- Where your input might be required
Tip: Many statuses relate to internal Development and QA stages. These will be visible to you but may not always require your action. Your Project Manager will confirm which statuses are most relevant for your involvement.
Updating Task Statuses
Statuses can be updated directly from within a task. To change a status:
- Open the task in ClickUp.
- Click on the existing status label near the top of the task.
- Select a new status from the dropdown menu.
Beware: The small '>' arrow next to the status name proceeds the status to the next status. In most cases this should be avoided.
2-Tier vs. 3-Tier Workflows
The workflow assigned to your project depends on your technical setup - specifically, how many environments (like staging or development) are used.
Most projects follow the 3-Tier Workflow (Development → Staging → Production), but some projects use a simpler 2-Tier Workflow (Staging → Production). Your Project Manager will clarify if 2-Tier is used on your setup.
Statuses Explained
| Name | Description |
|---|---|
| Open | Initial state for all new tasks. |
| Blocked | The task cannot be progressed due to a blocker or question that needs to be answered. |
| In Progress | The task is currently in progress. |
| In PR | Author has submitted a pull request so the work can be code reviewed by the rest of the development team. |
| Awaiting Deploy to Dev | Sometimes used by the developer as part of an automated merge, but hasn't been confirmed as deployed to the Development environment. |
| In Developer Review | The task has been deployed to the Development environment ready for the author to sense check before passing this over to Plume QA for detailed testing. |
| Ready for QA on Dev | Task is ready to be reviewed by Plume QA on the Development environment. |
| Passed QA on Dev | Task has been approved by Plume QA and is ready to proceed to the Staging environment. |
| Failed QA on Dev | Task has been rejected by Plume QA and needs to be reviewed by the developer. |
| Ready for QA on Staging | Task is ready to be reviewed by Plume QA on the Staging environment. |
| Passed QA on Staging | Task has been approved by Plume QA and is ready for ready for client testing, where required, before production deployment. |
| Failed QA on Staging | Task has been rejected by Plume QA and needs to be reviewed by the developer. |
| Ready for Client Testing | The task is ready to be reviewed by the client, prior to being deployed to a Production environment. |
| Passed Client Testing | The task has been approved by the client and is ready to be deployed to the Production environment at the next opportunity. |
| Failed Client Testing | The task has been rejected by the client and needs to be reviewed by Plume. |
| Deployed to Production | The task has been deployed to the Production environment, where the client is free to confirm the task has been delivered as expected. Tasks in this state are automatically resolved after 30 days of inactivity. |
| Task Completed (Non-Code) | Used for non-code related tasks. The task has been completed to the best of the individual's knowledge, and requires the Project Manager to review and close the task if no further action. |
| Resolved | This is the overall "Closed" state in ClickUp. Whilst Deployed to Production and Task |