Answers to common questions about setting up Nexus, managing tests in Jira and connecting your existing tools. For a walkthrough, start with the setup guide.
Getting started
What is Nexus?
Nexus is test management for Jira Cloud. Your team can design test cases, organise test sets, plan cycles, record results and trace testing back to requirements from inside Jira. Test Cases, Test Sets and Test Executions are real Jira work items.
Who needs to set it up?
A Jira administrator installs Nexus and runs Nexus Setup from the Apps menu. Start with one pilot project, add the Test Case, Test Set and Test Execution work types, then check the project's health before running your first test. The setup guide covers each step.
Does it work with team-managed projects?
Yes. Nexus supports both company-managed and team-managed Jira Cloud projects. Team-managed projects have their own work types and workflows, so use Nexus Setup → Team-managed Projects to configure each project. Setup explains the manual steps and checks that the project is ready.
Can I use Nexus with Jira Data Center?
Nexus is built for Jira Cloud on Atlassian Forge. It is not a Jira Data Center app.
Licensing and AI
Do I need AI to use Nexus?
No. Nexus includes all features. Test design, manual and exploratory execution, test data, model-based testing, CI result ingestion, environments and releases, and reporting all work without an AI account. AI requirement analysis and test generation switch on when a Jira administrator connects your own account with Anthropic, OpenAI, Google, Moonshot Kimi or xAI Grok. A person accepts every AI draft. See pricing for licensing information.
How are licensing and AI usage billed?
Atlassian Marketplace handles Nexus licensing and billing. AI features use the AI provider account connected by your Jira administrator; that provider bills your organisation separately for model usage. Contact nexus@resync.co.nz for pricing questions.
Does AI create test cases automatically?
Tests generated from a Jira requirement are drafts for your team to review and edit. Accepting a draft creates the Test Case. Model-based testing has a separate creation workflow: generating cases from a model creates Jira Test Cases directly after you choose that action. Review the resulting cases before marking them Ready.
Test management
How do test cases, test sets and executions fit together?
A Test Case describes what to test, including its steps and expected results. A Test Set groups cases. A Test Execution records a run and its results. Use cycles to organise planned testing and track progress in the Test Hub.
Can I link testing to requirements and defects?
Yes. Link test cases to Jira requirements to track coverage, and link defects to failed runs. This lets your team follow the evidence from a requirement through its tests, results and related bugs. The product guide explains the workflow.
Can I bring in existing test cases?
Export a folder with or without sub-folders as CSV, JSON, Excel or Cucumber .feature files. Import .feature files into folders using @folder: tags. Test Sets and cycles support JSON export and import for a round trip, and CSV export. Imports preview first and can be undone. Migrate from Xray, Zephyr Scale, Zephyr Squad or AIO Tests; trial a representative sample and reconcile the imported records before switching over. See the migration checklist.
Can I format test steps?
Yes. Steps, preconditions and free-text cases support bold, italic, inline code, code blocks, bulleted and numbered lists, and links. A small toolbar and preview help you check the result. Existing plain cases are untouched until someone turns formatting on.
Can we search testing data with JQL?
Yes. Alongside the existing functions, use executedBy, runsWithStatus (including custom run statuses), testsInSet and requirementsWithoutTests. For example, issue in requirementsWithoutTests("ABC") finds requirements in ABC with no tests.
How does Nexus handle larger test libraries?
The repository and test-case pages read Jira data directly from the user's browser, reducing server-side Jira API calls. Nexus is built to stay fast for large teams. This does not establish a specific concurrent-user limit.
Automation and integrations
Can Nexus receive results from our automated tests?
Yes. Playwright (Nexus reporter), Selenium with pytest (Nexus pytest plugin), Cypress (reporter or JUnit upload), Cucumber (JSON upload), JUnit (XML upload) and Mocha (mochawesome JSON upload) have all been verified against the current development build. Robot Framework also works. Results match by Automation Key or issue key, record pass/fail per run and can raise a linked Jira Bug for failures. The automation guide covers configuration.
Does Nexus run automated tests inside Jira?
Use Run in CI on a cycle to start GitHub Actions, GitLab.com, Azure DevOps Pipelines or Bitbucket Pipelines. Tests execute in your CI infrastructure and results come back into the same cycle. A project administrator connects the service once and chooses which context values Nexus sends. Tokens stay in Forge secret storage, are never shown again and are deleted when the connection is removed. A double press within 60 seconds is blocked and every request is audited.
Can we use Jenkins or self-hosted GitLab?
Yes. A Jenkins job can upload results with the same Nexus upload tool. For self-hosted Jenkins or GitLab, Nexus can queue Run automation for the customer-hosted nexus-runner, which runs tests and posts results back. Direct Run in CI connections are for the four cloud-hosted services listed above.
Is there an API for reading test data?
Yes. A project administrator separately enables Read test data on a key. It is off by default and never added to existing keys. The read-only API returns that project's test cases, cycles, runs, step results and coverage as paged JSON. Jira issue-secured records are excluded, sensitive values are always masked, and people appear only as Atlassian account IDs. Each key is limited to 60 requests a minute and 2,000 an hour. See the API reference and Read API OpenAPI file.
Data and support
Where is our test data stored?
Nexus runs on Atlassian Forge, with test data stored in Jira and Forge storage. When your team uses AI features, the content needed for the action is sent to the provider your Jira administrator connected. Read the privacy policy for the details.
Where can I get help?
Email nexus-support@resync.co.nz with your Jira site address, the page you were using and what happened. Include the error message or a screenshot if you can. Please leave out passwords, API keys and sensitive customer data. The support page lists support hours and urgent contact details.