Project milestones
Break a Project into ordered, dated planning stages with explicit lifecycle state, collaborative descriptions, and Issue progress.
Project milestones are called Phases inside Integrity. They are ordered planning stages inside one Project. Use them to describe meaningful delivery steps, assign linked Issues to a stage, and see which stage is current without adding another manual status system.
Where to manage Phases
Open a Project and use the Phases section on Overview. People with Project metadata edit capability can:
- create a Phase with a name and optional target date
- rename it or change its target date
- drag the diamond handle to reorder stages
- expand the row to write a collaborative phase description
- copy a URL that opens the Project Issues table filtered to that Phase
- move the Phase through its allowed lifecycle states
- delete the Phase
The display number is assigned by Integrity and does not change when you reorder or rename a Phase. Copied links therefore remain stable.
Lifecycle states and Issue progress
Phase lifecycle is explicit and independent from assigned Issues:
| State | Icon | Meaning |
|---|---|---|
| Upcoming | Empty gray diamond | Work has not started. |
| Current | Amber diamond with a small gem inside | This is the first unresolved stage in Project order. |
| Completed | Solid green diamond with a check | The stage was explicitly completed. |
| Cancelled | Solid red diamond with a cross | The stage was intentionally stopped. |
| Deferred | Gray diamond with pause bars | The stage was intentionally postponed. |
Issues that belong to no Phase show a dotted diamond labeled No phase.
Issue counts remain useful progress information, but completing or reopening every assigned Issue does not complete or reopen the Phase. Empty Phases show their lifecycle state instead of 0% of 0. Hidden private-Team Issues never contribute to counts shown to someone who cannot access them.
Repository-linked Phases use the same lifecycle. A phase becomes completed only after Integrity accepts the verified build checkpoint for that exact phase; a running agent or execution lease is not completion evidence.
Collaborative descriptions
Expand a saved Phase row to author its phase narrative. The editor uses the same collaborative Tiptap/Yjs document system as Project and Initiative content, including rich blocks, links, images, autosave, and visible human-approved model suggestions.
Each Phase has one primary description document inherited from its Project. It is intentionally not a supporting Resource: it has no standalone Phase route, does not appear in search or Favorites, and cannot receive independent sharing.
Dates and Project schedule
A target date is optional. If a new or changed target date falls outside the Project's planning window, Integrity asks whether to keep the Project dates or extend the schedule when you have permission to do so. Choosing either option uses one authorized save.
Delete behavior
Deleting a Phase is permanent. Assigned Issues stay linked to the Project and their Phase assignment is cleared. The Phase description authority is removed, while Activity and audit evidence retain display-safe event-time snapshots.
Phases are Project planning stages. They are not Product Versions, release contexts, approvals, or workflow statuses.
Related
The Project overview guide describes the Phase dependency graph and the execution milestones a run reports. These execution states are separate from a Phase's planning lifecycle and Issue counts. Whole-Project orchestration through a configured host was retired on 2026-10-13; each Phase is built and delivered in its own pull request.
Phases on Issues
Assign Issues, use Shift+M, filters, grouping, views, and Activity.
Phases on the Timeline
Inspect and move dated markers on workspace and Initiative timelines.
Projects
Use Project detail, properties, Issues, Activity, and planning views.
Collaborative authoring
Understand the shared document editor and human-approved agent suggestions.