Repository navigation
pm Milestone type should support parent linking and progress tracking #155
Description
Issue
Milestones are a valuable PM type that was completely unused in our project until this audit. After creating them, we found that:
- No progress tracking: Milestones don't show progress (e.g., how many child epics/tasks are complete vs open).
- Calendar warning on create: Creating a Milestone without a deadline/reminder/event shows a warning 'Milestone has no deadline/reminder/event — it will not appear on the calendar.' This is correct but the warning could be more helpful by suggesting the exact command to add a deadline.
- Child item count: It would be useful if
pm get <milestone_id>showed a count of child items and their status breakdown (e.g., '3 open, 1 in_progress, 12 closed').
Suggested Improvements
- Progress indicator: When viewing a Milestone, show child item status summary (X/Y items closed, A open, B in_progress).
- Helpful create warning: In the calendar warning, suggest:
Add a deadline: pm update <id> --deadline 2026-07-01 - Milestone roll-up: Support
pm aggregate --parent <milestone_id>to see status breakdown by child type. - Milestone close semantics: When all child items are closed, suggest closing the milestone.
Context
We created 4 milestones (M1-M4) for our game project phases and wanted to see progress towards each milestone.
Activity
unbraind commentedon Jun 10, 2026
Partial on @unbrained/pm-cli 2026.6.9:
pm aggregate --parent <milestone_id> --group-by status(or--group-by type,statusfor a combined breakdown) gives the child status summary today. Supported group-by fields: parent, type, priority, status, assignee, tags, sprint, release.--parentlinking like any other item.Remaining: child status summary surfaced directly in
pm get <milestone_id>(#1), a more actionable calendar warning — it still emits the barecalendar_item_without_schedule:<id>:no_deadline_or_reminder_or_eventwith no suggested command (#2), and close-suggestion semantics when all children are closed (#4). Leaving open.pm context --depth full + --parent subtree scope; pm list --no-trunca…
unbraind commentedon Jun 14, 2026
Verified already shipped and now documented/closed via #234: pm get returns child rollup (count/active/by_status) for Milestone/Epic, calendar warning suggests pm update --deadline, and pm aggregate --parent works.
unbraind commentedon Jul 11, 2026
pm tracker item:
pm-gcm3— pm get: include child rollup summary for Milestone/Epic items (pm Milestone type should support parent linking and progress tracking #155)