Soon, users will be able to select attachments directly from Jira work items such as specifications, documents, wireframes, and spreadsheets and include them as trusted context when generating AI-powered test cases.

Selected attachments will be:

This capability will be available across Vansah Advanced edition.

Vansah now comes in two editions to give teams the flexibility to choose the level of intelligence, governance, and scale that best fits their needs.

Customers will be able to upgrade or downgrade instantly between editions directly from the Atlassian Marketplace inside Jira with no reinstall required.

Vansah now supports exporting BDD-style Test Cases directly as Cucumber .feature files, enabling seamless integration with Cucumber-based automation frameworks and BDD workflows.

This feature allows teams to reuse BDD Test Cases authored in Vansah and execute them externally using standard Cucumber tooling.

We’ve refined the Vansah board layout by removing a redundant header and simplifying the board structure. This update improves vertical space usage, aligns the header and ensures page content expands resulting in a cleaner, more focused working experience.

We’ve introduced Testing Scope as an optional control in Vansah Intelligence Test Case Generation, giving teams greater precision over how AI designs test cases.

Testing Scope uses existing Jira labels to guide Vansah Intelligence toward a specific testing focus such as negative, boundary, migration, performance, or error-handling scenarios without requiring any changes to how requirements are written.

Available as an optional dropdown during AI generation, Testing Scope integrates seamlessly with your current Jira workflows. If no scope is selected, Vansah behaves exactly as before, ensuring predictable and backward-compatible results.

Any selected Testing Scope is automatically linked to the Test Case Label field, making it easy to identify, organize, and differentiate test cases across your test repository.

In our last release, Vansah introduced Test Data Collections a major step forward in how teams manage and reuse test data across test cases, executions, and cycles.

Now, we’re completing that vision with the introduction of embedding Test Data Parameters into Test Scripts.

Test data is no longer static text locked inside steps. Instead, variables from your Test Data Collections can be inserted directly into test steps and scripts, allowing the same test logic to adapt seamlessly across environments, users, configurations, and scenarios.

We have introduced Iterations to Test Data Collections a powerful way to define a variable once and execute it across multiple data rows.

With Iterations, a single test case can now validate multiple scenarios without duplication. Easily model positive, negative, and edge-case data variations using the same test logic.

What this enables

This enhancement transforms test data from static, single-use values into a dynamic, reusable data layer, enabling broader coverage, faster execution, and more resilient testing at scale.

Because Epics represent a roll-up of child and linked work items, the standard Vansah Test Management panel isn’t always the right fit.

This update replaces that experience with an interactive traceability summary at the Epic Work Item level, allowing teams to immediately understand and manage testing across the full scope of an Epic.

With the Epic Traceability View, you’ll be able to: