Test management tools have a way of drifting from the rest of Jira over time: a separate hub to open, a defect that already exists somewhere else, a status you have to check one item at a time. None of it is a single big problem. It adds up anyway, one extra click at a time.
Appsvio Test Management 5.8.0 is four changes aimed at that accumulation, not at any one feature in isolation.
Watch the recording here: What's new in Appsvio Test Management (ATM) 5.8.0
If you've ever had more than a handful of test cases in a single Test Execution, you know the drill: open one, change the status, close it, open the next. Now you can select several Test Case Executions at once and assign them to one person or change their status in a single action.
Logging a defect from a Test Case Execution used to mean creating a new Jira issue every time, even when the same bug had already been reported somewhere else. You can now search for an existing defect and link it directly from the TCE view instead.
Checking for defects used to mean opening every test case or test plan one by one. The Test Execution tab inside Test Case and Test Plan views now shows a defect count, with a direct link to the issue navigator. (The Test Case Execution tab already had this; the Test Execution tab does too now).
Test Management now sits fully inside Jira's own navigation instead of living in its own separate space. Admins get a direct Configuration shortcut to Environments and Test Steps.
Manual expand/collapse on the test cases field, a direct navigator link copy option from the Test Repository, a lock on accidental status changes on iterations, and more reliable column handling on import.
Teams without a dedicated test management app usually handle defect tracking through manual issue links or spreadsheets, which gets harder to maintain as the backlog grows. If you're weighing that trade-off, happy to answer questions about how this works in practice.
Learn more about Appsvio Test Management for Jira at Atlassian Marketplace
Darek Jaron
0 comments