KEEP XRAY TEST COVERAGE HONEST BEFORE EVERY RELEASE.
Connect Xray to Menza and ask about tests, test plans, test sets, preconditions and executions in plain English — what's failing, what's never been run, whether the release is actually covered. Menza reads it live through the official Xray API, and when something needs organising it acts only once you approve.
- Reads developer data
- Can take action on Xray, once you approve
- Connects via the official API
What can Menza do with Xray?
Fill coverage gaps before the release cut
Menza finds test plans with untested or failing areas, proposes the test sets and executions that would close the gap, and — once you approve — creates them in Xray, ready for the sprint.
See failures with their history attached
Ask why a test plan went red and Menza reads each failing execution alongside the test's recent history, so you can tell a real regression from a flaky step in one answer.
Answer 'are we ready to ship?' with data
Ask for a release's execution status — passed, failed, never run — across its test plans, and get the honest coverage picture in one message instead of five Jira boards.
See these answers on your own Xray data.
Menza working with Xray.
Menza doesn't just answer questions about Xray — it proposes the fix and, once you approve, does the work. You stay in control; nothing changes until you say go.
Menzajust now31 tests in plan 'Release 5.4' have never been executed — 12 of them cover the new payments flow. I'll group the 31 into a test set and create an execution assigned to this sprint.
Menza6m agoTest 'Checkout-Timeout-Retry' has failed in 4 of its last 5 executions after passing for six months. I'll add it and its two preconditions to the regression test plan for triage.
Connect Xray in a couple of clicks.
Is my Xray data secure?
Your credentials are encrypted at rest and never exposed to the AI. Menza reads your data through the provider's official API using the access you grant, and you stay in control of what it can do — read-only by default, with any actions gated behind your approval.
Read our privacy policy- Encrypted in transit and at rest
- Scoped access — you choose what Menza can see
- Read-only by default; any action needs your approval
- Credentials are encrypted and never shown to the AI
- Revoke access at any time
Xray questions, answered.
How does Menza connect to Xray?
With your Xray API credentials — entered once, encrypted at rest, and never shown to the AI. Menza authenticates server-side and reads your testing data through the official Xray API; there's nothing to export from Jira.
What can Menza answer about my Xray data?
Tests, test steps, preconditions, test sets, test plans and executions. Ask which tests in a plan have never run, what's failing in the current release, how pass rates trend by component, or which preconditions a test depends on.
Is my Xray data safe with Menza?
Yes. Your credentials are encrypted and never exposed to the AI, and Menza reaches only the projects your key can see. Any change it proposes — a new test set, plan or execution — waits for your explicit approval first.
Does it work across our Jira projects?
Yes. Xray data lives against your Jira projects, and Menza can filter by project the way you would with JQL — ask about one release in one project, or compare coverage across every project your credentials reach.