Integrity
FeaturesFeature Phases

Manage Feature Phases

Break a Feature into ordered, dated planning stages with explicit lifecycle state, collaborative descriptions, and Issue progress.

Beta

Feature Phases are ordered planning stages inside one Feature. 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 Admin Editor

Open a Feature and use the Phases section on Overview. People with Feature 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 Feature 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:

StateMeaning
UpcomingWork has not started.
CurrentThis is the first unresolved stage in Feature order.
CompletedThe stage was explicitly completed.
CancelledThe stage was intentionally stopped.
DeferredThe stage was intentionally postponed.

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 Feature 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 Feature. 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 Feature schedule

A target date is optional. If a new or changed target date falls outside the Feature's planning window, Integrity asks whether to keep the Feature 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 Feature 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 Feature planning stages. They are not Product Versions, release contexts, baselines, approvals, or workflow statuses.

On this page