How to Edit a Task's Activity Status in Task22

Task activity status is the field that tells everyone where a piece of work actually stands. In Task22 every task carries its own editable activity status, and this guide shows exactly how to change it.

The four activity statuses

Task22 uses four activity statuses, and you can rename or extend the list to match how your team already talks about work:

• Open — the task is live and someone is working on it.
• Pending — the task is waiting on something: a reply, an approval, a delivery, or another task finishing first.
• On hold — the work is deliberately paused and not expected to move until someone unpauses it.
• Closed — the work is finished, cancelled, or otherwise resolved.

Status is set per task, not per project. Two tasks in the same project can sit in different statuses at the same time, which is what makes a board or a dashboard trustworthy.

How to edit a task's activity status

1. Open the Tasks view. Sign in and go to Tasks in the top navigation. This is the same view you land on after sign-up.
2. Find the task. Search by title, filter by assignee, or scan the board columns. Each column groups tasks by their current activity status.
3. Open the task. Click the task title to open its detail panel. Start date, end date, assignee, and activity status all live on the task itself.
4. Edit the status. Open the Status field on the task and pick a value: open, pending, on hold, or closed. The change saves to the task immediately.
5. Confirm where the work moved. Close the panel. On the board the task now sits in the column for its new status. In list view the status column shows the new value. On any dashboard that reads from that project, the status counts update with it.

You can also change a status from the board itself: drag a task from one status column to another, and the task's activity status is updated to match the column you dropped it in. Both routes edit the same field, so there is no separate board status to keep in sync.

Status is not the same as a date

This comes up often, so it is worth being precise:

• Dates describe when work should happen. Task22 supports a start date and an end date on each task, which can be adjusted manually or automatically as the plan moves.
• Activity status describes what is true right now. It is set by a person, not derived from dates.

A task can be past its end date and still marked open — that is a signal, not a bug. A task with no dates can be closed. Because status is explicit, a dashboard built on it reflects what people actually decided rather than a guess.

Keeping statuses honest

Status is only useful if it is current. A few habits that keep it that way:

• Change the status the moment work changes state, not in a Friday cleanup.
• Use pending for blocked work and on hold for work you chose to pause; collapsing both into open hides the difference between waiting and stalled.
• Close tasks when the deliverable exists, not when someone remembers.
• Review the pending and on hold columns in your weekly meeting — those two lists are where slippage hides.

Where status shows up

Because the status lives on the task, everything built on top of tasks inherits it: board columns, list views, per-assignee workload, and dashboard counts by status. One edit on one task corrects every view that was showing the old value, without anyone re-entering data in a second tool.

If your team also keeps a status column in a spreadsheet, that copy is now the least reliable place to look. Point people at the task instead.