Release notes·April 30, 2026·2 updates

Background sub-agents and richer Jira tickets

2 updates shipped on April 30, 2026.

Update 01 of 02
Better Jira tickets
Issues filed to Jira now include the test goal, expected result, and the actual steps the agent took.
When QA.tech files a Jira ticket for an issue it found, the ticket now contains the full context developers need to triage and reproduce: test goal, expected result, and the exact sequence of steps the agent took. Previously the ticket only contained a link back to QA.tech, which assumed the developer had access.

This is most useful for teams where not every developer has a QA.tech account, or where Jira is the canonical issue tracker. (We extended the same upgrade to Linear, Trello, and Slack a few days later – see May 5.)
# Direct link
Update 02 of 02
Sub-agents run in the background
Long-running chat tasks no longer block the conversation.
When the chat agent kicks off a sub-agent for a longer task (an evaluation, a deep crawl, an exploratory run), that sub-agent now runs in the background. The conversation stays responsive, you can keep typing, and the result drops back into the thread when it's done. While the sub-agent is working you'll see real-time progress and the human-readable name of whatever it's currently doing, not a generic spinner.
# Direct link

Better Jira tickets