Milestones
Milestones represent release checkpoints, sprints, or customer commitments. They connect requirements, test runs, and defects so you can measure readiness in one place.
Creating a milestone
Capture:
- Name & description – Communicate scope and expectations.
- Milestone type – Choose from organisation-defined types (e.g., Release, Sprint, Hotfix). Mark a type as default if most milestones share the same behaviour.
- Start & target dates – Used for timeline tracking and analytics.
- Active flag – Active milestones appear in dashboards and filters; inactive ones remain for history.
Usage
- Test runs – Link runs to a milestone to roll up pass/fail rates, execution progress, and time spent.
- Defects – Filter defects by milestone to track blocking issues before release.
- Requirements – Associate requirements to spot scope creep or outstanding work.
- Analytics – The project overview and milestone dashboards show completion trends, defect burndown, and outstanding tests for each active milestone.
Tips
- Keep milestones lightweight—create them for the checkpoints you report on regularly.
- Use milestone types to drive reporting slices (e.g., quarterly release vs. weekly regression).
- Archive a milestone (
active = false) once the release ships; historical metrics remain available in exports.