[ Concepts · Milestones ]
Milestones
A milestone is an outcome-shaped deliverable with a target date, priority, status, optional start date, and the issues assigned to it. Milestones can also depend on other milestones or cycles.
Milestones give agents a shipping lens. They group issues by outcome and expose progress, dependency, and target-date context without flattening everything into one backlog.
Shape
- name
- string
- Milestone title.
- description
- string?
- Goal and scope.
- priority
- priority?
- Relative planning importance.
- startDate
- number?
- Set when work first starts.
- targetDate
- number
- Intended completion timestamp.
- status
- active | completed | missed | canceled
- Milestone state.
- completedAt
- number?
- Completion timestamp.
- dependencies
- edges
- Optional milestone or cycle blockers and related items.
Lifecycle
- active: the goal is open.
- completed: all work is done or the milestone is manually completed.
- missed: the target was not met.
- canceled: the goal is no longer planned.
- Hydrant can record startDate when an assigned issue enters a started status and can complete active milestones when all assigned issues are terminal.
How It Appears In MCP / REST
MCP
create_milestone({ name, targetDate, status: "active" })
list_milestones({ spaceId })REST
POST /api/v1/milestones
GET /api/v1/milestones?spaceId=...