Resync Labs · Built for Jira Cloud

Nexus. Test management that lives inside Jira.

Test cases, cycles, coverage and release evidence as real Jira issues. AI drafts your team reviews and approves. A release decision you can explain.

Jira tracks the work. It does not track the testing.

Out of the box, Jira has no test case, no test cycle and no test run. It cannot tell you which requirements are tested, against which build, in which environment, with which data. Teams fill the gap with spreadsheets, a second tool, or tickets standing in for tests. Nexus puts the missing pieces inside Jira, as real Jira issues.

Nexus requirement coverage report showing covered, partial and untested requirements, sample projectNexus cycle execution screen showing a failed test run and its linked defect, sample project

What you can do with it

From requirement to sign-off, in the tool your team already lives in.

Tests are Jira issues

Test Cases, Test Sets and Test Executions are native Jira issues, with the workflows, links, permissions and JQL your team already governs.

Run it, raise the defect

A step-by-step runner captures evidence per step. A failed step can raise a Bug linked to the run, the test case and the requirement.

Design tests your way

Step tests, Gherkin, data-driven iterations and shared steps. Model-based testing turns states and decision tables into test cases, no AI needed.

AI drafts, people decide

Analyse a requirement for ambiguity and gaps, then review editable test drafts. Only the drafts you accept become Jira Test Cases.

Coverage you can prove

See every requirement as covered, partly covered, failing or untested, with the tests, results and open defects behind each status.

Evidence that knows when it is stale

Results are tied to builds and environments. A newer deployment flags earlier results as stale before anyone signs off.

Why teams choose it

  • One record, not five tools: requirements, tests, runs, defects and approvals stay linked in Jira.
  • Evidence you can defend: every result carries its build, environment and test data, so sign-off rests on current proof.
  • Automation in the same view: send JUnit, Cucumber, Playwright and other results from your CI. Your tests run in your infrastructure.
  • AI with a review gate: drafts stay drafts until a person accepts them. Until an administrator connects an AI account, Nexus uses no AI.
  • Test data you can trace: datasets are versioned, classified and reserved, with a scanner that flags real personal information.
  • Your testing, portable: export to CSV, JSON or Cucumber .feature files at any time, and bring tests in from a CSV export.

Who it’s for

For Jira teams who need to show their testing, not just do it.

QA leads & testers

Design, run and report on testing without leaving Jira or maintaining a second system.

Release managers

A current, explainable view of readiness before the go or no-go call is recorded.

Jira administrators

Guided setup for company-managed and team-managed projects, with a health check that flags drift.

Frequently asked questions

Where does Nexus keep our testing records?

Core test artefacts are Jira issues. Supporting records such as runs, datasets, environments and audit entries use Atlassian Forge storage, and Nexus has no separate Resync application backend.

Does Nexus use AI by default?

No. AI features run only when a Jira administrator connects your organisation’s own AI account. Every generated test is a draft until a person accepts it, and release approval is always a human action.

How is Nexus priced and when is it available?

Nexus is one edition with everything included. It is being prepared for the Atlassian Marketplace, which will publish the current price and handle licensing, billing and the free trial.

Release with evidence, not assumptions.

Nexus is being prepared for the Atlassian Marketplace. See the product guide, or talk to the team about a pilot on one real release.