# Cross-test PR verdicts, mobile build numbers, and per-run outbound IP > 6 updates: PR review verdicts now weigh all of a PR's tests together, Search your entire Jira or Linear backlog from chat, Clearer CORS failures in… Source: https://qa.tech/changelog/2026-07-08 --- 6 updates shipped on July 8, 2026. In this release 1. 01[PR review verdicts now weigh all of a PR's tests together](#2026-07-08-pr-review-verdicts-across-tests)Highlight 2. 02[Search your entire Jira or Linear backlog from chat](#2026-07-08-chat-tracker-search-full-backlog) 3. 03[Clearer CORS failures in network logs](#2026-07-08-clearer-cors-failures) 4. 04[Mobile build numbers on results, and downloadable preview builds](#2026-07-08-mobile-build-numbers-and-preview-downloads) 5. 05[Every test run now shows its outbound IP](#2026-07-08-outbound-ip-per-run) 6. 06[PR review chats now stay in one conversation](#2026-07-08-pr-review-conversation-continues) 1. Highlight Featured this release ## PR review verdicts now weigh all of a PR's tests together The PR review agent assesses every test in a run side by side instead of one at a time, catching failures that share a root cause. Previously, each test in a [PR review](https://qa.tech/product/pr-testing) was assessed on its own. Now the same agent that reviews the PR looks at all of its test results together, so it can catch cases where several tests fail for the same underlying reason – a shared login step, for instance – instead of reporting them as unrelated failures. Tests still being assessed show as "Awaiting assessment" in the test composer while the agent works. This builds on the [diff-anchored verdicts](https://qa.tech/changelog/2026-07-01) and [self-repair](https://qa.tech/changelog/2026-07-02) work from the past week. [\# Direct link](#2026-07-08-pr-review-verdicts-across-tests) 2. Update 02 of 06 ## Search your entire Jira or Linear backlog from chat The chat assistant's tracker search is no longer capped at 25 issues – ask about your backlog and get up to 500 results back. If your project has Jira or Linear connected, asking the [chat assistant](https://docs.qa.tech/core-concepts/ai-chat-assistant) to look up tracker issues now returns far more than a first page of 25. Large backlogs are searchable in one go, up to 500 issues at a time. [\# Direct link](#2026-07-08-chat-tracker-search-full-backlog) 3. Update 03 of 06 ## Clearer CORS failures in network logs Test run network logs surface preflight requests and the exact reason a CORS request was blocked. Preflight (OPTIONS) requests now appear in network logs with a "Preflight" badge and are searchable by that term. Requests blocked by CORS show a "CORS" label with a plain-language reason – like a missing `Access-Control-Allow-Origin` header – and the server's actual response headers, so you can see exactly why the browser rejected the call instead of a bare failed request. [\# Direct link](#2026-07-08-clearer-cors-failures) 4. Update 04 of 06 ## Mobile build numbers on results, and downloadable preview builds Test results now show the exact build number, and preview mobile builds can be downloaded straight from the Preview Environments card. [Mobile test results](https://qa.tech/product/mobile-testing) now display the build version and number (e.g. `v1.2.3 · (42)`) pulled straight from the uploaded APK/IPA, so you can pin a failure to the exact build. Preview environments created via CI/CD now show a platform badge, file name and size for mobile builds, with a download icon to grab the APK/IPA directly – matching the download experience already available on permanent environments. Promoting a preview environment to a custom one now carries its linked mobile build along with it. [\# Direct link](#2026-07-08-mobile-build-numbers-and-preview-downloads) 5. Update 05 of 06 ## Every test run now shows its outbound IP See the exact public IP address your target app saw during a run – handy for allowlist and firewall debugging. The run test case result page now has an "Outbound IP" field with a copy button, filled in live as the run executes. It pairs with the [mobile testing IP ranges](https://qa.tech/product/mobile-testing) already available for allowlisting, but gives you the precise address for that specific run. Also exposed via the [API](https://docs.qa.tech/api-reference/introduction) as `outboundIpAddress` on run test case responses. [\# Direct link](#2026-07-08-outbound-ip-per-run) 6. Update 06 of 06 ## PR review chats now stay in one conversation Re-running a PR review continues in the existing conversation instead of starting a fresh chat every time. When `@qatech` reviews the same pull request again – after new commits, for example – it now reuses that PR's existing review conversation instead of spinning up a new chat each time, so the full [PR review](https://qa.tech/product/pr-testing) history stays in one thread. The `change-review` [API](https://docs.qa.tech/api-reference/introduction) behaves the same way; pass `forceNewConversation: true` if you want a clean conversation instead. [\# Direct link](#2026-07-08-pr-review-conversation-continues) ## 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