OPEN Release: Last updated 26th of February 2025
What's New
Create Advanced Test Plans (ATP) with Empty JQL Results
Vansah Test Management for Jira now allows users to create an Advanced Test Plan (ATP) even if the JQL or Jira Filter used does not currently return any issues.
Previously, Vansah required that a JQL query or filter to return at least one Jira issue before an ATP could be created. This meant that if a test plan was based on a JQL that initially had no results, users were unable to proceed.
With this update, users can now:
Create an ATP even if the JQL query does not return any issues, as long as the query itself is valid.
Automatically see issues appear in the ATP once they match the JQL conditions over time.
Why This Matters?
This enhancement provides greater flexibility for testers who want to set up their test plans at the beginning of a release cycle, even if the relevant Jira issues have not yet been added.
Call Test Case - Modular Test Design
We are thrilled to announce our latest Call Test feature designed to revolutionize the way you manage your Test Case libraries. We understand the importance of efficiency and reusability in testing processes so we have introduced a modular test-case design approach to boost the reusability of your Test Case libraries.
With this new feature, you can now insert Test Cases directly within your Test Case scripts. This approach emphasizes breaking down Test Cases into small, reusable pieces, eliminating the need for duplicating or copying and pasting. By adopting this modular design, you can achieve greater testing efficiencies and streamline your workflow.
Playwright and Vansah Test Management for Jira using TypeScript
We're excited to announce that TypeScript support is now available for Playwright in conjunction with Vansah Test Management for Jira. For more details on how to get started with this new TypeScript support, please refer to our Git repository. For other Bindings please visit our Playwright page.
New Test Case Owner & Test Case Assignee for Testing
Test Case owner is used for Test Cases to represent who is responsible for designing and managing the Test Case. During Test Case execution you can select an Assignee to be responsible for the Test Case execution. Here is a summary:
Test Case Owner:
Responsible for developing and maintaining the Test Case
The person who creates and manages the Test Case and Versions
Test Case Assignee:
The person assigned to execute the specific Test Case against a linked requirement (Jira Issue, Test Folder or Test Plan)
Can change based on the current testing phase or project needs
Enhanced Bulk Test Case Update Functionality Across Jira Projects
Vansah will soon allow comprehensive bulk update capabilities that transcend project-specific limitations. Users can now:
Update Test Cases across multiple Jira projects simultaneously
Select project-specific fields dynamically
Customize updates based on unique project configurations
Previously, bulk updates were restricted to the current project. Now, Vansah intelligently adapts to varying project structures, allowing you to:
Select different Test Case types per project
Map and update fields with project-specific values
Streamline test management across diverse project environments
More information on Bulk Update
Enhanced Folder Visibility with Total Count Feature
We've introduced a new total count feature for test folders. This enhancement displays the aggregate number of test cases across the root folder and all its subfolders, providing you with an instant overview of your test repository structure.
How does it benefit you?
Instant Insight: At a glance, you can now see the total number of test cases within any folder, including all its subfolders.
Efficient Navigation: Quickly identify which folders contain test cases without the need to expand each one individually.
Where can you see it?
The new total count appears next to each folder in your test repository view. For example, you might see something like "Regression 39/440", indicating that the Regression folder contains a total of 39 Test Cases while combining this folder along with sub folders contain 440 test cases.
Bug Fixes
Issue Key | Area | Description |
VANS-179 | Export | Exporting Test Step and Expected isn't exporting "& < >" characters |
VANS-1971 | Cloning | Cloning a test folder with the "Copy Test Cases" option does not associate the active version of test cases from the original folder |
VANS-3438 | Test Folder | Linking a Test Case in Folder screen, does not update the count in Test Folder |
VANS-3364 | Test Case Versioning | Switching version from v2 to v1 as active does not change the count for Jira Issue (Linked) column |
VANS-3471 | Bulk Update | Deleting a Test Case(s) is not updating the count for Test Folder under Test Repository |
VANS-3606 | Cloning | Vansah is confusing with reference to, "Copy Test Cases" and "Clone Test Cases" when using Clone Test Folders feature. It should be Re-use Test Cases instead of Copy. |
VANS-3642 | Test Plan | Test Plan status is not updating the Overall Result correctly to reflect on executed test cases. |
VANS-3357 | Migration | Plain Text Script Display Issue in Migrated Test Cases from Zephyr Scale to Vansah |
VANS-3488 | Export | Exporting Test Scripts from Test Folder using selection, incorrectly exports the default Test Case version instead of the active Test Case version. |
VANS-3702 | Navigation | Server not responding error occurs when a user clicks on Test Case Back button and then clicks on the Browser Back button from the Vansah board. |
VANS-3734 | Import | Vansah's Import error message is not descriptive enough to inform user of invalid or incorrect Jira Issue keys when linking Test Cases on import. New Error message now lists the invalid Issue Keys on import. |
VANS-3496 | Test Cases | Linking the same Test Case with new Test Cases, results in error "Couldn't verify one or more cases. Please ensure Test Cases are valid" |
VANS-3720 | Test Cases | Test Case reload issues after navigating back from 'ALL Test Cases' Page |
VANS-3879 | Test Execution | Test Results from a Test Plan are not being updated on the Jira Issue when Sprint is not active. |
VANS-3738 | Import | Importing Owner as a field is not supported during import Test Cases process. See Importing Test Cases for new Owner field. |