When a developer opens a Jira ticket, the first question is usually the same: has QA been through this yet, and did it pass? Until now the answer lived somewhere else — a test management tab, a Slack thread, a stand-up. Arqo closes that loop: it posts a rich test summary as a comment on the ticket, and from today it keeps that same comment updated with live Pass / Fail / Blocked results as your test runs complete. One comment. Always current. Right where the work happens.
The problem with test results and Jira
Most teams handle this one of two ways, and both go stale. Either QA pastes a summary into the ticket once and never updates it — so the comment says '15 test cases written' long after 3 of them failed — or every run adds a new comment, and the ticket turns into a scroll of near-identical updates nobody reads. Developers stop trusting the comments and go back to asking in Slack.
The fix isn't more comments. It's one comment that tells the truth.
How it works
Generate test cases from a Jira ticket in Arqo with 'Comment on Jira' switched on, and Arqo posts a formatted summary to the ticket — every test case, neatly grouped, in Jira's native rich formatting (real status chips, not plain text).
Then, as you execute those cases in a test run — manually or with Playwright MCP — Arqo finds its original comment and edits it in place. Each case gets a live status chip: green for passed, red for failed, yellow for blocked. The comment header shows the aggregate at a glance — all green only when every case passes.
- One comment per ticket — updated in place, never duplicated
- Per-case status chips in Jira's native formatting (ADF), not pasted text
- An aggregate header — PASSED, MIXED, or FAILED — visible without expanding anything
- Works for manual runs and Playwright MCP agent runs alike
- Updates land automatically when a run completes — nobody has to remember
What the developer sees
A ticket with the Arqo comment answers the status question in one glance: which acceptance criteria have test coverage, which cases passed, which failed, and which are blocked. When QA re-runs after a fix, the same comment flips to green — no new notification noise, no archaeology through comment history. The ticket becomes the single source of truth for both the requirement and its verification.
Note: Failed cases raised as defects link back too: Arqo can raise a Jira defect as a sub-task of the parent story, with the failure evidence attached — so the trail from requirement to test to bug is unbroken.
Why this beats a dashboard link
We could have posted a link to an Arqo report and called it a day. But every link is a context switch, and every context switch is a reason not to look. Developers live in Jira; the results should meet them there. The full detail — evidence screenshots, step-by-step results, history — is still one click away in Arqo, but the answer to 'is this tested and passing?' never leaves the ticket.
Set it up in two minutes
- Connect Jira in Settings → Integrations (an API token with comment permissions is all it needs)
- Generate test cases from any Jira ticket with 'Comment on Jira' enabled
- Run the cases — in a manual test run or with the Playwright MCP agent
- Watch the ticket comment update itself as results come in
That's it — no webhooks to configure, no automation rules to write. If you're already generating test cases from Jira tickets in Arqo, the live updates just started working. And if you're not: connect Jira, pick a ticket, and let Arqo write the test cases for you. The ticket will tell you how they went.