Use test plan history to review recorded changes, see who made them, and check when they happened. You can review the plan’s history across testing cycles or focus on the activity for one iteration.
Open the plan’s history
Open Vansah in your Jira space and select Test Plans.
Open the test plan you want to review.
Open the three-dot More options menu near the top-right corner.
Select History, described in the menu as Revision History.
The timeline shows recorded plan changes and related execution activity. Entries include the time, a description of the change, and the person who made it. Where relevant, an entry identifies the iteration and test case.
Review one iteration’s history
Use the plan’s Iteration selector to choose the testing cycle.
Open Details.
In Activity, select History.
Use Newest first or Oldest first to change the order. Select Refresh to reload the activity.
This view includes execution records for the selected iteration, along with relevant plan configuration changes. A configuration entry marked All iterations affects the plan across its testing cycles, so it can appear when you review different iterations.
When an execution entry offers View test run, select it to inspect the run behind the change.
What the history can show
Change | What to look for |
Plan configuration | Plan creation and updates, plus requirements or test case links added or removed. |
Assignments | Changes to the plan owner or test case assignee, with the iteration or test case identified where applicable. |
Execution activity | Test runs created and result changes associated with the plan’s testing cycles. |
Bulk updates | A summary of how many test cases were updated and which fields changed. A single entry can summarize several changes. |
Use the right view for your task
Investigate a change: Use History to identify the change, time, user, iteration, and test case.
Review current testing progress: Use test plan reports in Insights.
Review actual results and evidence: Open the relevant test run.
History is a record of activity. Opening an earlier entry does not restore the plan or its results to that point in time.
If an entry is missing
Check the selected iteration, refresh Activity, and compare it with the plan-wide History menu. Bulk operations may appear as a summary rather than a separate entry for each test case. Changes shared by all iterations can appear in more than one iteration’s history.