Right now, Vansah permissions rely on Jira’s native project permissions and its not configurable! This doesn’t offer the level of granular control some teams need — especially in larger or more complex environments.

We're introducing new security features that allow you to define who can perform specific actions within Vansah — based on the user groups you've created in Jira.

This means:

Stay tuned for this update, as we continue to improve Vansah to better meet your testing management needs.

We’re thrilled to introduce the Vansah Intelligence (AI) Requirements Generator, a revolutionary tool designed to accelerate your planning process and eliminate the manual effort of writing requirements from scratch.

With the power of AI, Vansah Intelligence intelligently analyzes your attached documentation—including text, PDFs, Word files, images and soon videos to generate detailed user stories and requirements, ready to be available in your Jira project.

Whether you're launching a new feature or refining your backlog, the Requirements Generator helps your team move faster, stay aligned, and deliver with confidence. Dive into the full announcement and see how it works:
👉 Read the official post

We're excited to introduce a Comments Activity Section on the Vansah Test Run page!

With this new feature, you can now:

✅ Add comments directly within Test Runs
✅ Collaborate with your team in real-time
✅ Track important discussions and updates
✅ Improve test traceability and communication

We've enhanced the Create Test Case Version popup by adding a "DEFAULT" flag next to the default version in the dropdown. This makes it easier to identify which version is currently set as the default when creating a new test case version.

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.

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.

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.

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.

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:

Vansah will soon allow comprehensive bulk update capabilities that transcend project-specific limitations. Users can now:

Previously, bulk updates were restricted to the current project. Now, Vansah intelligently adapts to varying project structures, allowing you to:

More information on Bulk Update

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.

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.

​