Create and manage Milestones

A Milestone groups tasks toward an outcome with a planned end date. Open Milestones from your project. Milestones can overlap and work independently of Sprints and Plans. A task can belong to one of each at the same time.

• Milestones must be enabled in Project Settings. You can use them with Sprints switched off.
• Project members can view Milestones and prepare Planned Milestones. Team Leads and organization owners or admins with project access can start, complete, reopen, correct history, edit Current/Complete Milestones, and delete eligible Planned ones.
• Planned means prepared, Current means started, and Complete means completed. Several Milestones can be Current together. These labels are separate from task states such as Done and Closed.

Use All, Current, Planned, or Complete to filter the list. The view stays in the page address, so you can refresh or share it. Milestones are grouped by lifecycle and sorted by planned end, which does not set their start order.

Each card shows the title and planned end. Current and Complete cards show completed tasks out of the current or final included tasks; Planned cards preview scope. Select a card to see its Horizon, progress, objective, tasks, and history. Completing a Milestone does not mean every task is Done.

Only Done tasks count as completed work. Closed tasks remain unfinished scope. Tasks marked Exclude from metrics do not contribute to progress; an empty or fully excluded Milestone has no completion percentage. Progress unavailable means its saved evidence or current metric eligibility cannot be verified.

Past planned target means the date passed while the Milestone remains Current. The date never completes it, moves tasks, or rates delivery risk.

The Horizon at the top puts dates and progress together, using the same layout as a Sprint. Below it are the progress charts, boxed Objective, task states, membership, and Milestone history.

The timeline marks the start, planned end, and latest observed Now, with a diamond for the current or completed moment. Dates include the current organization time zone. until target and past target describe time remaining or elapsed. A Current Milestone continues past its target until a manager completes it.

Tasks completed and Total Size completed compare completed work with the plan saved at Start, also called the opening baseline, including Corrections. Total Size adds Coding-agent Mass and Person Weight using known estimates. Missing Size shows a dash; a known zero stays zero. The charts and Values & events explain remaining work and estimate coverage.

A Complete Horizon stops at completion and keeps its final values and planned-end marker. A Planned Milestone shows Planned end, Tasks, and Total size as a scope preview. A failed request offers Try again; missing saved evidence shows Progress unavailable while the title, dates, and objective stay readable. Milestones have no person-by-person Team Pulse.

Current and Complete Milestones show Task count and Size charts together. Select Total Size, Mass, or Weight without hiding Task count. Total Size stacks completed Mass and Weight, with a separate line for total known Size. The aligned Mass + Weight = Total Size values below it show Completed / total. Estimates do not represent hours or predict delivery.

The charts share the Horizon's time range. Future work stays blank, overdue work extends through Now, and Complete work stops at completion. A Correction updates the opening plan without a scope jump on the day it was recorded. A Scope change changes reporting from the time it takes effect. Reopening Done work reduces completion from that point.

Hover over a data point for values and local time to the minute; moving away hides the tooltip. You can also focus the chart and use the arrow keys. Expand Values & events for observations, recorded events, Completed, Remaining, total scope, and estimate/exclusion coverage. Times use the current organization zone.

Partial Size uses known estimates and shows coverage. If every estimate is missing, Size is unavailable while count can remain available. Unknown earlier task states can leave scope known but completion unavailable. Current progress refreshes while the page is open; missing saved evidence is explained rather than guessed.

Six cards show Backlog, Queued, Working, Reviewing, Done, and Closed. Working combines Agent working and In progress. These counts include metric-excluded tasks. Select a card to see matching tasks; select it again or choose Clear state filter to reset. Operational task lists let you open details or use a new-tab link.

The membership table below uses the Plan/Sprint columns and shows up to 20 tasks per page. Planning links to the task's other enabled planning records. Click a row, or focus it and press Enter, to open details. Mass/Weight is read-only; edit the task to change its live estimate. Complete pages keep saved outcomes despite later task changes. See Reset a task view for column widths.

Managers can search for a task to add or select Remove in the table. Other members can read the table and open tasks. A task has at most one current Milestone; adding a task already in another eligible Milestone moves its membership. Plan and Sprint membership stay unchanged.

Planned membership saves without classification. A change affecting a Current Milestone needs an explicit choice:

• Scope change means a new decision to add, remove, or resize work now. It changes reporting from this change onward and keeps the opening plan.
• Correction means the task and its Size should count in the opening plan, even if it was created later. Its real creation, state, and completion times stay unchanged. Before it existed, its completed contribution is zero; unknown earlier states stay unavailable. Only managers can choose Correction.

A move validates both Milestones together. If access or a record version changed, neither membership changes. Members can still make Scope changes through ordinary task editing.

On a Complete page, membership changes are saved Corrections only. They update that Milestone's report without adding live membership, changing the task, or affecting other planning records. Restoring a missing task requires proof of opening membership and its outcome at completion; today's task values cannot replace missing history. If a save is rejected, reload and review before trying again.

Select Create Milestone and enter a title, Markdown Objective, and Planned end. All three are required. Titles can repeat and you can add tasks later. The date means the end of that day in the current organization zone shown on the form.

Members can edit Planned Milestones; managers can also edit Current and Complete ones. Editing a Complete Milestone keeps its lifecycle and earlier details in history. Cancel leaves without saving.

Failed saves keep your draft. Fix highlighted fields and retry. If the record changed, use Reload and keep input, review your values, then save. Resolve access or feature changes first. Leaving a displayed target date unchanged preserves its original saved instant.

Managers start and complete Milestones in the browser.

On a Planned Milestone, select the green Start Milestone button, review the start time in the current organization zone, and confirm. The time cannot be edited in this dialog. Starting saves its tasks and estimates as the opening plan. Other Milestones stay as they are; several can be Current at once. Creating, editing, or reaching a planned date never starts or completes a Milestone automatically.

On a Current Milestone, select Complete Milestone. Review unfinished tasks, including metric-excluded tasks, and known Size. Completion date and time defaults to the current server time in the current organization zone. Keep it unchanged to preserve that exact instant, or edit the date, hour, and minute. The date picker has Apply and Cancel. A future time, a clock time skipped or repeated by daylight saving, or a past time unsupported by saved history is rejected.

Completion saves final membership, states, assignees, estimates, and progress, then clears every task's current Milestone membership. Queued, Working, and Reviewing tasks return to Backlog. Backlog, Done, and Closed stay as they are. Sprint and Plan membership, assignees, and work/review history remain. Resetting a task can change progress in a Current Sprint that also contains it, but not that Sprint's membership or opening plan. Completion does not accept reviews or stop an external agent; superseded runs cannot submit late work.

If the Milestone or tasks changed, use Reload Milestone, review the new effects and time, and confirm again. Failed actions keep the dialog and explain the problem.

Expand Milestone history for changes newest first. Each collapsed row shows a short description and when it was recorded, down to seconds. Search or filter to find a change, then expand it for who made it, before/after values, and saved evidence or revisions. Effective time is when a change applies to the Milestone; recorded time is when it was saved. Both use the current organization zone. Earlier facts remain inspectable after a Correction.

On a Complete Milestone, managers can open the separate estimate-correction disclosure to repair a saved estimate. Missing estimates stay missing; enter zero only when it is known.

A Correction updates the opening plan and final shortfall without adding a Scope-change event or changing the live task or completion time. For example, correcting an unfinished task's saved Size from five to three reduces the shortfall to three even after it returned to Backlog. Later live-task edits do not replace saved outcomes. Authorized Corrections and Exclude from metrics choices can change reporting.

On a Complete Milestone, choose Reopen Milestone and confirm the numbered dialog. It returns to Current and restores every member from its latest completion, including unfinished tasks returned to Backlog. Task states stay unchanged; it does not queue or start work, reopen tasks, or reopen a Sprint. Other Current Milestones and overlapping dates are allowed.

Reopening is blocked if a former member changed, was deleted, joined another Milestone, or history Corrections make restoration unsafe. No tasks are restored unless the whole action can succeed. Resolve the stated conflict and reload. If safe restoration is unavailable, you can continue managing the Complete record.

Completing it again saves a new final result. Earlier completion, reopening, and Corrections stay in history.

Managers can open the vertical three-dot More actions menu on a Milestone's detail or Edit page and select the red Delete Milestone action. It is enabled only for a never-started Planned Milestone with no task, draft, or publication references and no saved work history. Otherwise the disabled action explains what prevents deletion.

Changing only an unused Planned Milestone's title, objective, or planned end does not prevent deletion. Deleting it also removes those preparation edits and cannot be undone. It never deletes tasks. Current and Complete Milestones, task changes, and saved Corrections must remain available as work history. Deletion checks eligibility and the reviewed version again; reload if the record changed.

For a Building Task Builder draft, clear its Milestone assignment through the connected tool before retrying. A published draft's original reference stays as history; moving or clearing the live task does not remove it.

The CLI can create, list, read, and update Milestone details. Start, complete, reopen, and delete are browser actions; no CLI lifecycle or delete command is supported.

Use task create --milestone <milestoneNumber> to assign a new task, or task update <taskNumber> --milestone <milestoneNumber> to replace its Milestone. Omit the option to preserve membership or use --clear-milestone to clear it. task list --milestone <milestoneNumber> lists current members and combines with Plan and Sprint filters. Membership is independent of both other groupings and works with Sprints disabled.

Planned assignment needs no classification. Current membership and estimate changes require --milestone-change correction or --milestone-change scope-change. Correction requires management authority and can count a later-created task in the opening plan while keeping its real dates. Scope change applies from now. Complete Milestones cannot receive live tasks, and live estimate edits do not replace their saved outcomes. See Assign a Milestone and classify later changes for independent Sprint/Milestone choices, installed-CLI requirements, and recovery. The browser also supports membership and retained outcomes.

The browser label Current corresponds to the API/JSON state Started; retained storage values are unchanged.

Turning Milestones off in Project Settings hides their navigation and content but keeps records, targets, and history. Direct links show an unavailable page; managers can open Project Settings and members can ask a Team Lead. Turning the feature back on restores the same state.

CLI membership changes, filters, classifications, and estimate edits affecting Current Milestone history must wait until it is enabled. Rejection leaves the task and all affected histories unchanged. Browser estimate edits still collect an explicit Planning history change choice while the feature is off.

Use Clear state filter to remove a state-card selection without changing other task filters.

Drag a table header's resize handle to make room, or focus it, press Enter, and use the arrow keys. Press Enter or Tab to finish. Widths are remembered in this browser. Reset column widths restores defaults without clearing task filters. You can also scroll horizontally to reach all enabled columns.