Design reusable step-based, unstructured or BDD test cases.
Test management for Jira Cloud
Jira test management that keeps evidence connected
Plan, run and report testing beside the Jira work it proves. Nexus uses Jira issues for test cases, sets and executions, with supporting records held in Atlassian Forge storage.
How it works
What teams need from Jira test case management
A test repository is only useful when the team can connect a case to the requirement, execution, defect and release decision that gave it meaning.
Nexus keeps the core test artefacts in Jira so existing permissions, links, workflows and JQL remain part of the operating model. The Test Hub adds purpose-built planning, execution and reporting views without creating a separate account system.
Group tests into sets and cycles, assign work and record step results.
Bring uploaded automation results and manual runs into the same evidence model.
Trace requirements to tests, executions and linked Jira defects.
Export data and retain Jira issues if the app is later removed.
Implementation guide
Choose the workflow before the feature list
Start with one representative release. Map how requirements become cases, how tests enter a cycle, how failures become defects and who records the final decision. That path exposes fit more reliably than counting menu items.
For QA leads: repository structure, reuse, review and reporting.
For testers: a focused runner, evidence capture and defect creation.
For engineers: stable automation keys, result ingestion and CI examples.
For release owners: current environment evidence, gates and sign-off history.
Questions buyers ask
Frequently asked questions
Is Nexus a Jira Cloud test management app?
Yes. Nexus is built for Jira Cloud on Atlassian Forge. It does not use a separate Resync application backend.
Are test cases Jira issues?
Yes. Test Cases, Test Sets and Test Executions are Jira issues. Supporting run, data, environment and audit records use Forge app storage.
Can Nexus manage automated and manual tests together?
Yes. Manual execution and ingested automation results use the same traceability and reporting model. Test code still runs in your own CI, workstation or customer-hosted runner.
Test the workflow with a real Jira project
Start with one requirement, one cycle and one release decision.