Use the Vansah importer to create test cases or update existing ones from a CSV or Excel file. You can import test case details, test steps and links to Jira work items or Test Folders.
Start with the Test Case Import Template, or use your own file and map its columns to Vansah fields.
Before you begin
You need the Import Test Cases permission in the Jira space. Updating existing cases also requires permission to edit them; creating a new version requires permission to create test case versions.
Prepare a CSV or Excel (.xlsx or .xls) file, no larger than 5 MB. For Excel files, put the data on the first worksheet. Keep the column headings in the first row.
For updates, include a Case Key column. Include Case Version when you want to update a specific existing version. Case Version is separate from Release Version.
Import your file
Open your Jira space and select Vansah. On the Vansah Board, open the Settings cog and choose Import Test Cases.
On Setup, upload the file and select Next.
On Field Mapping, match the file columns on the left to the Vansah fields on the right. Choose None for columns you do not want to import.
If you mapped Case Key, choose Create new test cases or Update existing test cases. Confirm your choice when prompted.
Select Next to review Columns Validation. Correct any blocking errors before continuing.
When validation succeeds, continue to start the import. Review Results for each case’s key, version and outcome. You can open a successful case from the results to check it.
You can go back to correct a mapping without starting over. If the file itself needs changes, edit it and select Change file. You can upload the corrected file using the same filename.
Column guide
Your spreadsheet headings do not have to match the names below. On Field Mapping, select the corresponding Vansah field for each column you want to import. Leave fields you do not need unmapped. For a case with multiple step rows, put case-level values on its first row.
Keys and required fields
Vansah field | What to enter |
Case Key | Existing test case key. Required for updates. For new cases, leave unmapped to generate a key, or provide an available key. Example: |
Case Version | In update mode, enter the exact existing version to change. Leave blank to create a new version from the latest available version. This is the test case version, not a release. Example: |
Headline | Test case title. Required when creating a case; up to 800 characters. Example: Verify account login |
Case Type | Use a Case Type configured for the space. For new cases, map this field or select a Case Type during validation. Example: Functional |
Case details
Vansah field | What to enter |
Description | Describe the purpose and scope of the case. Example: Check a valid user login. |
Precondition | Describe the setup needed before execution. Example: User account exists. |
Test Case Status | Use a status configured for the space. Example: Draft |
Priority | Use an available Jira priority. Example: High |
Estimated Time | Enter a number of seconds, zero or greater. Example: |
Assignee | Enter the user's Atlassian account ID, not their email address. Example: Atlassian account ID |
Owner | Enter the owner's Atlassian account ID. Example: Atlassian account ID |
Created By | When creating cases, enter the creator’s Atlassian account ID. This column does not change the creator of an existing case in update mode. Example: Atlassian account ID |
Labels and links
Vansah field | What to enter |
Labels | Separate multiple labels with commas. Validation identifies labels that do not yet exist. Example: |
Component | Use existing Jira component names; separate multiple names with commas. Example: |
Link Requirement (Issue) | Enter Jira work item keys to link; separate multiple keys with commas. Example: |
Link Requirement (Test Folder) | Enter a folder path including the Jira space key and a trailing slash. Separate multiple paths with commas. Example: |
Link Test Case(s) | Enter existing test case keys to link; separate multiple keys with commas. Example: |
Test script
Vansah field | What to enter |
Step | Enter one action per step row. Put additional steps for the same case on following rows. Example: Enter valid credentials. |
Test Data | Enter the input values for the corresponding step. Example: Valid username and password |
Expected Result | Enter the expected outcome for the corresponding step. Example: Dashboard opens. |
Plain Text | Enter a free-form test script instead of step-by-step instructions. Example: Sign in and verify the dashboard. |
Automation | For new cases, enter the automation script content. To change an existing Automation script, open the case in Vansah and edit its script directly. Example: Automation script |
BDD - Gerkin | Enter a BDD script using Given, When, and Then. Example: |
Create new Test Cases
Choose Create new test cases to add cases to the repository. Provide a Headline and either map Case Type or select a Case Type during validation.
You may map Case Key to use keys from your file. Each key must be valid and available; an existing key cannot be used to create another case. Leave Case Key unmapped when you want Vansah to generate keys.
Update existing Test Cases
Choose Update existing test cases and map Case Key to identify each case.
Case Version in the file | What Vansah does |
An existing version, such as | Updates that exact version. |
Blank or unmapped | Creates a new version from the latest available version, then applies the imported data. |
Vansah reports a missing case key or a version that does not exist as an error. It does not substitute another case or version. Fields you leave unspecified are preserved. Imported step-based, Plain Text or BDD script content replaces the corresponding script on the version being updated. Review your file carefully before importing script changes.
Tip: To change a particular version without creating another one, map both Case Key and Case Version, and fill them in for that case.
Importing test steps
A case with several steps can occupy several rows. Put the case details, including its Case Key and Case Version when updating, on the first row. Use the following rows for its additional steps, leaving the case-level columns blank. Keep all rows for one case together so the additional steps attach to the intended case. A case can also be imported without steps.
Fixing import errors
Columns Validation shows field and row errors before import. Check that keys and versions exist when updating, required values are present when creating, and mapped values such as Case Type and Test Case Status are valid for the space.
The Results screen shows what happened to each case. An import can succeed for some cases and fail for others, so review the individual outcomes before retrying. If a new version was created before a later operation failed, use the version identified in the error when retrying; otherwise, leaving Case Version blank could create another version.