Linear Milestones
A project can run for months. Without checkpoints, nobody knows whether the team runs ahead or behind. Milestones split a project into clear stages, each with a name, a target date, and a group of issues.
What a Milestone Does
A milestone marks a meaningful point inside one project. It answers a simple question: what will be true when this stage ends? A good milestone describes a result, such as "Beta ready for testers", rather than an activity, such as "Do beta work".
Everyday Comparison
Imagine a road trip from Delhi to Jaipur. You do not drive blindly for six hours. You plan checkpoints: a breakfast stop, a fuel stop, and the city entrance. Each checkpoint tells you whether the trip stays on schedule. Milestones give a project the same checkpoints.
PROJECT: Mobile App Launch Milestone 1 Milestone 2 Milestone 3 Design approved Beta ready Public launch Target: Mar 15 Target: Apr 30 Target: Jun 10 [██████████] 100% [█████░░░░░] 50% [░░░░░░░░░░] 0%
Create a Milestone
- Open the project page.
- Find the Milestones section in the overview.
- Click the plus icon to add a milestone.
- Enter a name, an optional description, and a target date.
- Save the milestone.
Assign Issues to a Milestone
Open any issue that belongs to the project and set the milestone field in the right panel. Select several issues in a list and use the command menu for bulk assignment. Each milestone then shows a progress bar based on its issues.
Read Milestone Progress
The project overview lists each milestone with its date and completion percentage. A milestone that nears its date with a low percentage signals risk. Raise the concern early and decide whether to cut scope, add people, or move the date.
Milestone, Cycle, or Project
Beginners often mix these three. The table separates their jobs.
| Item | Scope | Time Pattern | Purpose |
|---|---|---|---|
| Project | One deliverable | Weeks to months | Deliver a full outcome |
| Milestone | One stage in a project | Specific target date | Mark a checkpoint |
| Cycle | One team's work block | Repeating, fixed length | Set a working rhythm |
A single issue can belong to a project, a milestone, and a cycle at once. Each label answers a separate question: which outcome, which stage, and which week.
Write Strong Milestones
Name the Result
Use phrases that describe a finished state. "Payments working in test mode" beats "Payments phase".
Keep the Count Small
Three to five milestones suit most projects. A long list hides the real checkpoints.
Set Honest Dates
Pick dates the team believes. Padded dates waste time, and unrealistic dates lose trust.
Example Plan
Project: Customer Portal M1 Login and profile ready Apr 5 12 issues M2 Invoices visible May 3 18 issues M3 Payments live May 31 15 issues M4 Public release Jun 14 9 issues
Each milestone gives the team a short-term target and gives stakeholders a plain view of progress.
Communicate Milestones to Stakeholders
Share the project link with stakeholders. They see each milestone, its date, and its progress at a glance. Use project updates to explain changes. A short note such as "Beta moved one week because payment testing needs more time" builds trust, since readers understand the reason and the new plan.
Handle a Missed Milestone
Missed dates happen. Review the cause, adjust the remaining plan, and record the new date. Avoid silent changes. Open communication keeps confidence high even when schedules slip.