Reuse a Test Case in another Jira space by linking the existing case, or create an independent copy when the other team needs to maintain its own tests. Choose the method based on whether you want to share the original Test Case or manage a separate one.
Choose a reuse method
Method | Use it when | What to check |
Link | You want the same Test Case to cover work items or Test Folders in another Jira space. | The original Test Case key is retained. Check the linked version and execution context. |
Clone | You need an independent Test Case that the destination team can change. | Choose the destination Jira space, folder, and properties to copy. The clone has its own key. |
Export and import | You want to transfer a set of cases using a spreadsheet. | Choose new-case import behavior and map only the fields and links you want in the destination. |
Before you begin
Confirm that you can access both Jira spaces and that Vansah is available in them. The linking and cloning workflows below use spaces on the same Jira site.
Check the source Test Case key and the version you want to reuse.
You need the relevant Vansah permission: link or unlink Test Cases, clone Test Cases, or export and import Test Cases. The destination must also be accessible to your account.
Link a Test Case from another space
For example, reuse DEMO-C46 from the DEMO space to test work item WEB-123 in the WEB space:
Open the destination Jira work item and its Vansah Test Management panel.
On Test Cases, select Link.
Use the Jira space selector in the linking dialog to choose the source space, such as DEMO.
Find and select the Test Case. Check its key and Version column. Keep any existing linked cases selected if you want to retain those links.
Select Apply. Review the additions and removals in the confirmation, check the destination, and select Apply again.
Confirm that the Test Case appears in the destination work item’s list with the expected key and version.
The screenshot shows where to open Link from a work item. For the Test Case’s own linking controls and Test Folder steps, see Linking Test Cases to Work Items and Test Folders.
A link uses a specific Test Case version. Do not assume that creating or changing the default version replaces every existing link. Check the version used in each work item, folder, or plan before executing it.
Clone an independent copy into another space
Find the source Test Case and open its More options (…) menu. Select Clone Test Case.
Review the headline and properties offered by the clone dialog, then select Next.
Use the Jira space selector to choose the destination space. Choose the destination Test Folder if you want the new case placed in one.
Review the destination and select Clone.
Open the created Test Case from the result and check its new key, script, properties, and links.
The cloned case is maintained independently. Changes to it do not update the source Test Case. See Cloning a Test Case for the full workflow.
Transfer cases with export and import
In the source Jira space, select the cases you need and export the Test Cases or their scripts to a spreadsheet.
Open Vansah in the destination Jira space. Open the Settings gear and select Import Test Cases.
Upload the file and review its field mapping. For new destination cases, leave Case Key unmapped so Vansah generates new keys. If you map Case Key, choose Create new test cases and use valid, available destination keys.
Review or leave unmapped any work item, Test Folder, and Test Case link columns so the import uses the links you intend. Check the destination Case Type and other mapped values.
Complete validation, start the import, and review each result. Open the new cases to confirm their content and destination.
See Importing and Updating Test Cases from CSV or Excel for supported columns, create/update behavior, and error recovery.
Check the reused case before testing
Confirm whether you are using the original linked case or a new copy.
Check the Test Case key, selected version, and Jira work item, folder, or Test Plan context.
Create the Test Run in the intended destination context and verify it in Test Runs. Linking a case does not copy its execution results into a new context.
Use labels, components, and folders to keep the cases easy to find, while checking which Jira space owns each Test Case.