Release Notes
This page contains gathered notes for each app release.
Version 4.5.0 (February 6th, 2026)
Testers can now refine existing Test Cases using the Rovo Agent. From the Ask Rovo or Improve options, the Agent analyzes current Test Steps, suggests improvements in a structured table, and, upon confirmation, updates the Test Case by creating a new version of the Test Steps. This ensures Test Cases stay aligned with changing Requirements while maintaining clear traceability of all modifications.
The Traceability Report can now be exported to a CSV file. This enables users to further analyze or share traceability data outside Jira, for example by loading it into spreadsheets or other reporting tools, while preserving the structure and relationships visible in the report.
We have updated the naming across the app: “Testing Setup” is now called “Testing Project.” This change aligns terminology with how users organize and manage their testing initiatives, without impacting existing configurations or data.
Version 4.4.0 (January 16th, 2026)
Users can now manage multiple iterations for a single Test Case. A new All Iterations tab within the TCE dialog provides a centralized view of execution history, allowing for direct status and assignee updates. Navigation has been streamlined with a "Back to all iterations" shortcut, and the specific iteration number is now clearly displayed during execution.
Administrators can customize the Test Step interface. Through the global settings, the visibility of the Action, Data, and Results fields can be toggled, and their display order rearranged via drag-and-drop. These layout changes automatically sync across the Test Case panel, full-screen view, and execution screens while ensuring all historical data remains safely stored.
The Configure layout button provides two tabs for report customization.
Work Item Layout: Users can add up to three additional fields (e.g., Priority, Sprint, Components) for Requirements, Test Cases, and Defects.
Testing Objects: Users can filter the visible elements. Options include:
Select all: Displays all columns and objects (default).
Only Requirements and Test Cases.
Requirements, Test Cases, and Test Case Executions.
The Export button generates a PDF based on the current view. Linked requirements are repeated in separate rows to ensure clarity.
Version 4.3.0 (January 8th, 2026)
A dedicated Import section is now available within the Testing Hub to facilitate data migration from external tools, specifically Xray. This functionality allows for the bulk transfer of Test Cases via .xlsx files, reducing manual data entry and minimizing migration errors.
Version 3.0.0
Bug Bounty Program
Appsvio Test Management is now an active participant in the Atlassian Bug Bounty Program.
Accelerate the learning curve with a pre-populated sample project. New users can generate a sample project during the initial setup to quickly familiarize themselves with the app features and interface before creating their own data.
Define test prerequisites using the new Preconditions custom field.
Test Case View: Use this field to document requirements (e.g., "User must be logged in," "Cart is empty") when designing the test.
Test Case Execution: Testers view these requirements in the Execution object window to verify the environment before starting the run.
Reuse test steps by embedding an existing test case within another test case. Use this feature to modularize your tests (e.g., creating a standard "Login" case) and insert them into complex scenarios to avoid unnecessary duplication.
The Test Case Architect (Rovo Agent) now supports preconditions. When you ask the agent to generate a Test Case, it automatically includes suggested Preconditions in its response alongside the Test Steps.
Version 2.0.0
Reporting & Defects
Traceability Reports: Introduced end-to-end reporting to track the lifecycle of requirements through to test execution.
Test Coverage Reports: Added visual coverage metrics to identify gaps in testing.
Defect Management: A new Environments custom field is now available on Defect work items, allowing for precise environment specification when logging bugs.
Last updated
Was this helpful?