Phase of Project or Milestones
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, Survey TesterSurveyTester gives you several views and tools to analyze project iterations.
4. How to Track Iterations Using Milestones
4.11. 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.
4.22. What You Will See After Creating Milestones
Once milestones are created, Survey TesterSurveyTester populates multiple features automatically:
a. Filter Issues by MilestoneMilestone:
You can filter issues to see: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 MilestoneMilestone:
Survey TesterSurveyTester visually separates issues by milestone so you can easily see: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 MilestoneMilestone:
When exporting screenshots, you can choose:choose -
- All screenshots in the project
- Screenshots for a specific milestone only
This enables milestone-based documentation for vendors, clients, or auditors.
d. Insights → Project PhasePhase:
The Insights section provides automatic analytics for each Milestone, such as: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:
Filtering issues by these statuses provides another layer of visibility into testing progress.
This can be used as a secondary or alternative method for tracking iteration loops.
5. Recommended Workflow for Measuring Iterations
- Create Milestone: Initial Link Shared
- Team tests → issues are logged
- Developer updates script
- Create Milestone:
UpdatedReadyBuildfor QC - Round 1 - Test again → new issues added
- Developer fixes remaining issues
- Create Milestone:
UpdatedReadyBuildfor 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.
6. 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
7. Conclusion
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.






