Clone a Test Plan to reuse its requirements and linked Test Cases for another testing activity. Vansah creates a separate plan with a new key and an initial iteration; it does not copy the original run history.
Before you begin
Check that you are cloning the intended plan. You need access to its Jira space and permission to create Test Plans.
Choose a clear name for the new activity, such as Checkout regression — release 2.0.
Review the plan’s requirements and case versions. Cloning the plan reuses Test Case links; it does not create independent copies of the Test Cases.
Clone the plan
Open the Test Plans tab in Vansah.
Find the plan and open its more options menu.
Select Clone Test Plan.
Enter the new Test Plan Name and review the copy options below.
Select Clone and wait for the new plan to appear.
Open it and review the initial iteration before executing cases.
Choose what to copy
Option | What it means |
Test Plan Name | Required, up to 255 characters. Give the new plan a meaningful name. |
Issues, Test Folders, Test Cases | Included in the clone workflow. These are links to the existing requirements and cases. |
Version | Copy the release version property. This is separate from the Test Case version. |
Environment / Sprint | Copy the corresponding execution properties. |
Planned start date / Planned end date | Copy the selected original dates. When not copied, the backend uses the current date, so review both dates afterward. |
Test Plan Folders | Link the new plan to the same organizing folders. |
The screenshots show an older layout. Some property controls depend on your configuration.
Check the new plan
Confirm the new plan name and key.
Review the requirements, Test Cases, active versions, assignments, and blocked state.
Check the planned dates and execution properties for the new activity.
Confirm the initial iteration and begin new execution when ready.
If cloning fails or times out, refresh the plan list before retrying so you do not create an unintended duplicate.
Clone or add an iteration?
Clone when you need a separate plan. Use a new iteration when you want another round of testing inside the same plan. See Test Plans and Test Plan Folders for related guidance.