# Tracker comments in chat and versioned CI mobile builds

> 2 updates: Chat agent reads issue comments from Jira and Linear, Custom version labels for API-uploaded mobile builds

Source: https://qa.tech/changelog/2026-07-03

---
2 updates shipped on July 3, 2026.

In this release

1.  01[Chat agent reads issue comments from Jira and Linear](#2026-07-03-chat-agent-reads-tracker-comments)
2.  02[Custom version labels for API-uploaded mobile builds](#2026-07-03-custom-version-labels-api-uploads)

1.  Update 01 of 02
    
    ## Chat agent reads issue comments from Jira and Linear
    
    Ask about a specific ticket and the chat agent now pulls in the full comment thread, not just the ticket fields.
    
    When you ask the [chat agent](https://docs.qa.tech/core-concepts/ai-chat-assistant) about an issue by key – "what's going on with PROJ-123?" – it now includes every comment on that issue (author, body, timestamp) alongside the ticket metadata. Works for both Jira and Linear connections.
    
    Comments are only fetched when looking up a specific issue by key, so searching or listing tickets stays fast.
    
    [\# Direct link](#2026-07-03-chat-agent-reads-tracker-comments)
    
2.  Update 02 of 02
    
    ## Custom version labels for API-uploaded mobile builds
    
    Builds pushed from CI can now carry a version label instead of showing up as "(undefined)".
    
    The Create Application Build [API](https://docs.qa.tech/api-reference/introduction) accepts an optional `version` field, so [mobile builds](https://qa.tech/product/mobile-testing) pushed from Bitrise, GitHub Actions or any other CI pipeline get a meaningful label like `1.2.3` in the environment name.
    
    Without it, QA.tech still falls back to the version extracted from APK/IPA metadata, or the file name as a last resort.
    
    [\# Direct link](#2026-07-03-custom-version-labels-api-uploads)
    

## 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