Why it matters
Milestones with progress gives ForkMesh a concrete mechanism for release goals with live completion bars. Group issues into milestones and watch live progress bars fill as work lands.
Planning loses force when it drifts away from the code history and pull requests it is supposed to guide. In ForkMesh, milestones with progress addresses that need at the feature level, keeping the behavior close to the repository instead of buried in a detached hosted layer.
How ForkMesh handles it
ForkMesh handles milestones with progress through the same split it uses across the product: issues are repository-linked records surfaced in desktop and web views beside branches, pull requests, milestones, and agent sessions.
The behavior is intentionally narrow: Group issues into milestones and watch live progress bars fill as work lands. State changes stay portable because the planning layer follows the repository instead of one private dashboard.
Where it fits
Use milestones with progress when triage and progress tracking should live beside the repository and remain portable.
It pairs with the rest of Issues & planning because Milestones with progress keeps release goals with live completion bars connected to the repository, its signatures, and the nodes that serve it.