Project Phase & Milestone Tracking

Clients often ask how they can measure the number of iterations (back‑and‑forth rounds) made to a survey link from the moment the initial link is shared until final sign‑off.
SurveyTester provides a flexible way to track these stages using Milestones / Phases, which allow teams to measure time, effort, and iteration counts across the project lifecycle.

How to use Milestones and related features to track testing phases, issue cycles, and iteration progress?

You can track each phase of the testing process by creating Milestones that represent each round of changes or review cycles.
Milestones allow you to monitor:

How many testing rounds occurred
When each round started and ended
How many issues belonged to each iteration
How long each milestone took
Which issues were resolved before moving to the next phase

Once you create multiple milestones, SurveyTester gives you several views and tools to analyze project iterations.

How to Track Iterations Using Milestones

1. Create Milestones for Each Round

Milestones can be created based on:

Each round of testing (Round 1, Round 2, Final QC, Sign‑off, etc.)
Significant project events (Initial Link, Major Script Update, Final Review)
Team processes (Ready for QC, Script Update Needed)

You can add a new Milestone whenever:

This creates a clear historical timeline of testing iterations.

2. What You Will See After Creating Milestones

Once milestones are created, SurveyTester populates multiple features automatically:

a. Filter Issues by Milestone: You can filter issues to see -

Total issues raised in each iteration
How many were resolved
Which require follow-up
Average resolution time per round

This helps quantify the effort per iteration.

b. View Issues Grouped by Milestone: SurveyTester visually separates issues by milestone so you can easily see -

Number of issues per testing cycle
The progression of quality from early rounds to final sign‑off
Which rounds were most effort-heavy

c. Exporting Screenshots by Milestone: When exporting screenshots, you can choose -

All screenshots in the project
Screenshots for a specific milestone only

d. Insights → Project Phase: The Insights section provides automatic analytics for each Milestone, such as -

Duration per phase
Workload per round
Counts of issues, comments, resolutions
Performance comparisons across milestones

This is the closest tool for calculating iteration effort.

e. Creating Phases Using Issue Statuses

In addition to milestones, you can structure workflow phases using:

Ready for QC
Script Update Needed

Filtering issues by these statuses provides another layer of visibility into testing progress.

Recommended Workflow for Measuring Iterations

Create Milestone: Initial Link Shared
Team tests → issues are logged
Developer updates script
Create Milestone: Ready for QC - Round 1
Test again → new issues added
Developer fixes remaining issues
Create Milestone: Ready for QC - Round 2
Continue until final sign‑off
Create Milestone: Final Sign‑off

In the end, the total number of milestones = total number of iterations.

Combined with timestamps, this gives you a clear record of project effort.

Benefits of Using Milestones for Iteration Tracking

✅ Understand total number of revision rounds
✅ Calculate testing time per iteration
✅ Show clear progress and quality improvements
✅ Provide transparency to clients or vendors
✅ Make audits and post‑project reviews easier
✅ Create an organized test history

Survey Tester does not directly label iterations automatically, but Milestones provide a powerful and structured way to track every phase, measure time and effort, and count the full number of iteration cycles.

By consistently creating milestones for each test round or build update, teams gain complete visibility from the initial link to final sign‑off.