PM Goals
Hierarchical goal tracking for Mission Control workspaces: workspace-scoped objectives that sit above individual boards, each with an owner, a target date and a health status, nestable under a parent goal, with progress derived from linked boards or set by hand, plus comments and a field-level activity feed.
On this page
Hierarchical goal tracking for Mission Control workspaces: set objectives, link them to boards, and track progress automatically or manually.
What it is
Goals are workspace-scoped objectives that sit above individual boards. Each goal has a title, description (up to 5000 characters), optional owner, target date, and a status that reflects health: on track, at risk, off track, or achieved.
Goals support hierarchy via parent_goal_id, letting you nest sub-goals
under a parent. Progress tracking uses two modes: auto (derived from
its child goals) and manual (explicit 0-100 percent set by the user).
A direct percent update on an auto goal is refused with a clear error once
that goal has a child goal to derive from; a goal with no child goals takes
a percent either way, and the derivation takes over as soon as a child
arrives. The goal dialog offers a Progress field wherever the number is
writable, so a brand-new goal can be given a percent at creation.
You can link any number of PM boards to a goal. Linking gives the goal concrete backlog items to track against. An activity feed records every change (status, progress, board links, parent changes) with field-level detail.
Where to find it
Goals live in the Mission Control PM system, inside a workspace. The goals list is the entry point — every goal in the workspace, with its health status and progress — and selecting a goal opens its detail view, carrying the description, owner, target date, linked boards, comments and the activity feed. Goal comments are their own thread, separate from that activity feed. The feed shows the newest 50 entries first, and a Load More button at its foot brings in the next 50 whenever older entries exist.
The same surface is reachable without the UI: the CLI control server exposes
/pm/goals, so a session or an external script can create, read and update
goals programmatically.
How it behaves
- Create -- defaults progress to 0 (callers can set 0-100) and status to
on_track; validates parent goal exists and is live; uses request deduplication - Update -- field-level activity logging via
logGoalFieldChange(only logs fields actually included in the patch) - Link / Unlink boards -- connects goals to PM boards for context and (in auto mode) progress derivation
- Nest --
parent_goal_idenables hierarchical goal trees;listChildGoalsreturns sub-goals - Comment -- separate comment system (add, list, delete) alongside the activity feed; a reply is created with
parentId(the comment it answers), andGET /pm/goals/:id/commentslists every comment withparentId(null when top-level) beside the rawparent_id, so a caller reads the link back under the name it wrote it with (the goal twin of BUG-207) - Delete -- cascading soft delete of the goal and all its descendants (children, grandchildren, etc.), plus their board links and activity
- Orphans read as root goals -- a goal whose parent was deleted or no longer exists comes back with no parent (
listGoals,getGoal,listChildGoals, so the Goals page, the CLI and the IPC channels agree), so it shows as a top-level goal and can still be edited; the goals export puts it at the top level with an empty Parent Goal ID. Nothing is rewritten in the database: the stored link is only cleared when the goal is next saved (BUG-146)
Sharing between teammates
Goals and their links to boards are shared across a workspace's members: one person creates, edits, re-links or deletes a goal and every other member of that workspace sees it on their next sync. A team guest sees no goals, because a guest is invited to individual boards and a goal belongs to the workspace. Goal comments and the activity feed are not shared yet.
The sync pulls the workspace's goals and links in one bounded snapshot and pushes this computer's changes; the later save wins a same-instant conflict, and anything already on a computer when sharing first turns on is uploaded rather than discarded.
Related
Goals are one part of the Mission Control PM system, so mission-control.md is the parent page to read next. If what you want is a rollup of the boards a goal points at, pm-portfolios.md covers grouping several boards into a named portfolio with a unified status summary — portfolios aggregate boards, goals sit above them as objectives. The full list of library pages is in INDEX.md.
Last verified 2026-11-04