Project status
Show where a Project is in its workspace lifecycle and configure the available statuses.
Overview
A Project status communicates its current planning stage. Status appears in Project tables, boards, timelines, detail properties, filters, grouping, and Activity.
Changing status is a deliberate action. Integrity does not automatically complete a Project when all linked Issues or Phases are complete; a connected coding agent's delivery events are the exception described below.
Change a Project's status
Select the current status in a Project row, Board card, Timeline property, or Project properties panel, then choose the new value. If you can edit Project metadata, the new status appears optimistically and is confirmed by the server. A failed save restores the previous value.
Select multiple Projects in List view and choose Actions → Status to update them together. Bulk actions affect only the selected Projects you are authorized to edit.
Status follows agent delivery
When a connected coding agent delivers a Project through a pull request, its status changes at delivery events rather than through typed commands. Starting Build moves the Project to In Progress and records which agent holds it. Requesting the independent reviewer moves it to In Review.
Merging the pull request moves the Project to Completed once the closure checks pass. Depending on your project's policy, you or the agent merges the pull request after all required review, verification, and acceptance checks pass. If a closure check fails, the Project stays In Review and the agent reports the reason.
Status categories
Each status belongs to a lifecycle category such as backlog, planned, in progress, completed, or canceled. Categories give tables and lifecycle controls a stable meaning even when workspace administrators customize the displayed status name and color.
Completed and canceled Projects are treated as closed. Use Show closed projects in Display options to include recently closed or all closed Projects in List and Board views.
Archive is not a status. A closed Project keeps its status when it is archived, and it is archived only automatically, after the delay your workspace sets. See Archived Projects.
Backlog or Planned
Two categories hold work that has not started, and they mean different things.
| Category | Use it for | What it says |
|---|---|---|
| Backlog | Ideas and proposals | Written down, not committed. Nobody has decided to do it yet. |
| Planned | Committed work that has not started | The decision "we are doing this" has been made. |
Put a new idea in a Backlog status, even a good one. Move a Project to a Planned status when you commit to it. That move is a decision, so make it on purpose rather than to tidy a list.
The difference matters because of Readiness. A Planned Project with no open blocker is Ready: it is committed and nothing is in its way, so someone can pick it up. A Backlog Project is neither Ready nor Blocked, because nobody has committed to it. See Readiness for how the mark is worked out.
Your workspace can rename these statuses, so look at the category in Workspace Settings → Projects → Statuses when the names differ. Integrity AI and connected coding agents follow the same rule: when you share an idea without committing to it, they create the Project in a Backlog status, and they use a Planned status only when you say the work is committed or ask for that status.
Configure Project statuses
Workspace administrators manage the Project workflow in Workspace Settings → Projects → Statuses. They can create statuses, change a name, description, color, or category, reorder the workflow, and select the default status used for new Projects.
The Automation section on the same page turns Project auto-archive on or off and sets the inactivity delay. It is on by default after 30 days. Every linked Issue must be archived or belong to an archived Team. Restoring the Project starts a new delay. See Archive and delete for release timing, archived pages and Restore.
A default status cannot be deleted. A status that is still assigned to Projects must be replaced or cleared according to the settings dialog before deletion can finish.
Project status and Project health answer different questions. Status describes lifecycle stage; health comes from the latest authored update and its freshness.
Permissions and history
Project metadata edit capability controls status changes. Workspace administration capability controls the shared status workflow. Status changes create Project Activity; settings changes remain part of the workspace configuration audit trail.