Milestones
Milestones represent release targets or sprint goals. Link test runs to milestones to track testing progress toward a release, and use sub-milestones to break large releases into manageable phases.
Creating a Milestone
Navigate to the Milestones tab in your project and click "+ New Milestone". Fill in the required fields to define your milestone's scope and timeline.
Required Fields
NameDescriptive name for the release or sprint (e.g. "Release v2.5", "Sprint 12", "MVP Launch").Start DateWhen testing begins for this milestone.End DateTarget completion date (the release or sprint deadline).Milestone Status Flow
A newly created milestone starts as Upcoming. Status transitions happen automatically based on dates, except for Completed which is set manually.
| Status | Code | Trigger | Visual |
|---|---|---|---|
| Upcoming | upcoming | Start date is in the future. | Blue badge |
| In Progress | started | Start date has passed; milestone not yet completed. | Indigo badge |
| Overdue | past_due | End date has passed but not all tests are complete. | Red badge |
| Completed | completed | Manually marked as complete by an Admin or Member. | Green badge |
Linking Test Runs
Link test runs to a milestone when creating the run, or afterward from the run detail page. Multiple runs can be linked to a single milestone to cover different test types (regression, smoke, feature).
Progress Calculation
Milestone progress is calculated as the ratio of test cases with a final result (passed, failed, or blocked) to the total test cases across all linked runs.
Milestone Detail Page
- Overall progress bar with passed/failed/blocked segment breakdown.
- All linked test runs with their individual progress displayed.
- Linked discovery sessions for exploratory testing context.
- Activity timeline showing recent test results, run completions, and status changes.
- Failed and blocked test cases listed for quick triage, grouped by run.
- Jira issues linked from failed test results (requires Jira integration).
Sub-Milestones
Create sub-milestones to organize large releases into phases. Each sub-milestone has its own test runs and progress tracking, and rolls up into the parent milestone's aggregate progress.
Creating a Sub-Milestone
On the Milestones page, click the "+ Sub" button on any existing milestone. The new milestone is automatically nested under the parent.
Example Structure
The parent milestone's progress reflects the aggregate progress across all sub-milestones. Sub-milestones can be expanded or collapsed in the list view.
Roll-up 자동 집계
Sub milestone이 1개 이상인 parent는 Roll-up 모드로 자동 전환됩니다:
- 진행률 = (모든 sub TC + parent 직속 TC) 합산으로 자동 계산
- 상태 = sub들의 상태 조합으로 자동 결정 (수동 변경 불가)
- 기간 = date_mode="auto"이면 sub의 min(start)~max(end)로 자동 계산
- 🔄 Roll-up 배지가 parent 카드에 표시됨
기간 모드 (Date Mode)
Edit 모달에서 🔄 Auto / ✏️ Manual 토글로 전환할 수 있습니다. Manual 모드에서 sub의 기간이 parent 범위를 벗어나면 경고 배지가 표시됩니다.
Progress Tracking Dashboard
The Milestone Detail page serves as a comprehensive progress dashboard, combining test results, team activity, and timeline data in one view.
Overall Progress Bar
Visual percentage with color-coded segments: green (passed), red (failed), yellow (blocked).
Test Summary
Total tests, passed, failed, and blocked counts across all linked runs.
Time Tracking
Days remaining, days elapsed, and an overdue indicator if the end date has passed.
Run Contributors
Avatar stack of all team members who contributed results to linked runs.
Activity Timeline
Most recent test results, run completions, and status changes in chronological order.
Failed & Blocked List
All failed/blocked test cases grouped by run name, with author and timestamp for each.
Release Management Best Practices
Follow these practices to get the most value from milestones and ensure smooth, well-tracked releases.
- 1
Create a milestone per release
Name after the version number (e.g. "v2.5.0") so milestones are easy to identify in the list.
- 2
Set realistic dates
Align start and end dates with your sprint or release cycle. Overly optimistic dates create noise with overdue notifications.
- 3
Create focused test runs
Separate regression, smoke, and feature-specific runs. Link all of them to the same milestone for unified progress tracking.
- 4
Monitor the dashboard daily
Check overall progress and triage failed or blocked test cases promptly to avoid last-minute surprises.
- 5
Complete the milestone
When critical tests pass and you're confident in quality, manually mark the milestone as Completed to finalize the record.
Webhook Events
Overdue milestones automatically change status and trigger notifications. Available webhook events: milestone_started, milestone_completed, milestone_past_due. Configure in Settings → Integrations to receive Slack or Teams alerts.
Next Steps
Explore test runs to understand how progress is generated, or learn about exploratory testing with Exploratory.