# Background sub-agents and richer Jira tickets

> 2 updates: Better Jira tickets, Sub-agents run in the background

Source: https://qa.tech/changelog/2026-04-30

---
2 updates shipped on April 30, 2026.

In this release

1.  01[Better Jira tickets](#2026-04-30-better-jira-tickets)
2.  02[Sub-agents run in the background](#2026-04-30-sub-agents-run-in-background)

1.  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](#2026-04-30-better-jira-tickets)
    
2.  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](#2026-04-30-sub-agents-run-in-background)
    

## Your team moves fast. Can your testing keep up?

QA.tech agents test your product autonomously, so moving fast never means shipping broken. See how it works in a 30-minute demo.

[Get a demo](https://qa.tech/demo)

[QA.tech](https://qa.tech/)

SOC 2 Type 2 compliant

![Sensiba SOC 2 Type 2 compliant](https://qa.tech/assets/soc2-type2-badge-DPb1j9VX.png)

### Product

-   [Platform overview](https://qa.tech/product)
-   [AI QA Testing](https://qa.tech/ai-qa-testing)
-   [Web Testing](https://qa.tech/product/web-testing)
-   [Mobile Testing](https://qa.tech/product/mobile-testing)
-   [PR Testing](https://qa.tech/product/pr-testing)
-   [MCP](https://qa.tech/product/mcp)
-   [Use cases](https://qa.tech/use-cases)
-   [Changelog](https://qa.tech/changelog)

### Compare

-   [QA.tech vs Cypress](https://qa.tech/compare/qa-tech-vs-cypress)
-   [QA.tech vs Playwright](https://qa.tech/compare/qa-tech-vs-playwright)
-   [QA.tech vs Mabl](https://qa.tech/compare/qa-tech-vs-mabl)
-   [QA.tech vs QA Wolf](https://qa.tech/compare/qa-tech-vs-qa-wolf)
-   [AI vs Human QA](https://qa.tech/saas)

### Resources

-   [Docs](https://docs.qa.tech/)
-   [Blog](https://qa.tech/blog)
-   [Events](https://qa.tech/events)
-   [Pricing](https://qa.tech/pricing)
-   [Case Studies](https://qa.tech/case-studies)

### Company

-   [About](https://qa.tech/about-us)
-   [Partnerships](https://qa.tech/partnerships)
-   [Press](https://qa.tech/press)
-   [Contact Us](https://qa.tech/contact)
-   [Privacy Policy](https://qa.tech/privacy-policy)
-   [Terms of Service](https://trust.qa.tech/resources?s=mb9w4yjb03i3t8bjsq4jx3&name=main-agreement.pdf)
-   [Security & Compliance](https://trust.qa.tech/)

### Social

-   [](https://www.linkedin.com/company/qa-tech-ai/)
-   [](https://x.com/getqatech)
-   [](https://www.instagram.com/getqatech/)

© 2025 QA.tech. All rights reserved