Import test cases into Vansah to quickly build your repository from a spreadsheet or export from another system.
Before you begin
You need permission to manage Test Cases in the Jira Space.
Prepare your import file in the supported format. See template for reference.
Steps
Open Vansah in your Jira Space.
Go to Test Repository.
Select Import.
Choose your import file.
Map columns so Vansah knows where to find fields like title, steps, expected result, and folder.
Start the import.
Review the import summary and fix any rows that failed.
Frequently Asked Questions (FAQ)
Which file formats are supported?
Which file formats are supported?
Vansah supports importing test cases using CSV (.csv) and Excel (.xlsx) files.
Where can I get the import template?
Where can I get the import template?
Download the official import template . This is designed to help you with the appropriate columns. You may choose your own file and simply map them during the import process.
Can I import hundreds or thousands of test cases?
Can I import hundreds or thousands of test cases?
Yes. Vansah is designed to support bulk imports. For very large imports, consider splitting your data into multiple files for easier validation and troubleshooting.
Why does one test case in the template appear across multiple rows?
Why does one test case in the template appear across multiple rows?
Each row represents one test step.
The first row contains the test case information, while the following rows only contain additional steps.
Example:
Test Case | Step |
Login Test | Step 1 |
(blank columns) | Step 2 |
(blank columns) | Step 3 |
This tells Vansah that all three steps belong to the same test case.
Do I need to repeat the Headline, Description and other fields on every row?
Do I need to repeat the Headline, Description and other fields on every row?
No.
Only the first row of each test case needs to contain the test case details.
Subsequent rows should normally only contain:
Step ID
Step
Test Data
Expected Result
Can I import a test case without test steps?
Can I import a test case without test steps?
Yes.
Simply provide the test case information and leave the step columns empty.
Can I import only test steps into an existing test case?
Can I import only test steps into an existing test case?
No.
Currently, the importer creates complete test cases. It does not append additional steps to existing test cases.
Can I preserve my existing Test Case Keys?
Can I preserve my existing Test Case Keys?
Yes.
Populate the Test Case Key column to preserve your existing identifiers during migration, provided the key is valid and available.
What happens if I leave the Test Case Key blank?
What happens if I leave the Test Case Key blank?
Vansah automatically generates a new Test Case Key.
How do I import test cases into folders?
How do I import test cases into folders?
Use the Link Requirement (Test Folder) column.
Example:
Regression/Address/verification/
If the folder does not exist, Vansah will create it automatically during the import.
Regression/Address/verification/ |
Importing Test Cases with the folder path = Regression/Address/verification/ would appear as follows in Vansah. More info
Learn more how to easily copy existing Test Folder paths.
Can I create nested folders?
Can I create nested folders?
Yes.
Use forward slashes (/).
Example:
Regression Regression/Login Regression/Login/API/
Regression/Login/API/Authentication/
Can I link imported test cases to Jira work items?
Can I link imported test cases to Jira work items?
Yes.
Populate the Link Requirement (Issue) column with one or more Jira work item keys.
Example:
PROJ-101
Can I link multiple Jira issues?
Can I link multiple Jira issues?
Yes.
Separate issue keys using commas.
Example:
PROJ-10, PROJ-25, PROJ-38
Is Step ID mandatory?
Is Step ID mandatory?
No.
Step IDs are optional. If omitted, Vansah automatically numbers the steps.
Can I import test data?
Can I import test data?
Yes.
Use the Test Data column.
Example:
Username: admin Password: Password123
Can I import using users Atlassian email addresses?
Can I import using users Atlassian email addresses?
No.
The importer expects Atlassian Account IDs rather than email addresses.
Can I import multiple labels?
Can I import multiple labels?
Yes.
Separate labels using commas.
Example:
Smoke,Regression,API
What values are accepted for Case Type?
What values are accepted for Case Type?
Use an existing Case Type configured in your project.
Examples include:
Functional
Regression
API
Performance
The value must match an available Case Type.
Which priority values are supported?
Which priority values are supported?
Use priorities configured within your Atlassian workspace for the Jira space.
What format should Estimated Time use?
What format should Estimated Time use?
Estimated Time should be entered as a numeric duration (for example, seconds).
Example:
600
Why are some rows failing?
Why are some rows failing?
The most common reasons are:
Error | Cause | Resolution |
Invalid Case Type | Case Type doesn't exist | Use an existing Case Type |
Invalid User | Atlassian Account ID not found | Use a valid Account ID |
Invalid Jira Issue | Issue key doesn't exist | Verify the Jira issue key |
Duplicate Test Case Key | Key already exists | Remove or change the key |
Folder Path Invalid | Incorrect folder syntax | Use |
Missing Headline | Required field missing | Populate the Headline column |
Invalid CSV Format | Broken delimiter or encoding | Save as UTF-8 CSV |