Track Plane Cycle Progress with Scope and State Breakdowns
Open a started Plane cycle’s details panel to inspect progress and the remaining work by assignee, state or label. Read completion alongside scope changes before judging the sprint.
The cycle must be dated and started for chart data. Advanced progress charts and early lifecycle controls are plan-dependent; verify availability on the selected Cloud or self-hosted edition rather than relying on a chart entitlement assumption.
Example: a cycle that completes six items but adds five more needs a scope discussion. Inspect which work is still started, unstarted or blocked before announcing a delivery improvement.
Step-by-step guide
Open the correct active cycle
Select Cycles inside the project and open the intended cycle. Confirm its date range and project timezone; an undated draft does not have useful elapsed progress data.
Inspect the details panel
Open the sidebar panel beside the work-item list. Read completed work against total scope and, when point estimates are used, compare the effort view with raw item count.
Drill into the remaining work
Switch the breakdown from Assignees to States or Labels. Inspect the actual work behind a large unfinished category rather than interpreting it as an individual performance ranking.
Explain the delivery decision
Review added, removed and cancelled work and the current owners. Record whether the team should reduce scope, resolve a blocker or transfer unfinished work after the cycle ends.
Common mistakes
Comparing unlike scope snapshots
Added work changes the denominator. Keep the scope changes visible when comparing the current cycle with the original commitment.
Sources and verification
Based on product documentation checked on 2026-11-04. This is a documentation-based guide, not a hands-on benchmark. Features and availability can change.