01Why generate from Jira
Jira is where most teams track the work that needs testing. Re-authoring each ticket into test cases by hand is slow and goes stale. Generating cases directly from a Jira issue gives you a structured first draft mapped to your test template, linked back to the ticket so coverage is traceable.
02Connect Jira (one time)
An admin connects Jira Cloud as an integration source in Admin → External References → Sources:
- In Jira, generate an Atlassian API token for the account TestOrchestrator should authenticate as.
- In TestOrchestrator, Create a source, choose Jira Cloud, and set the Base URL (e.g.
https://yourcompany.atlassian.net). - Authenticate with the account email plus the API token.
- Test the connection, then assign the source to the right projects.
Full detail is in the Jira integration docs and the shared Integration Sources guide.
03Generate the cases
- Point the AI generator at the Jira issue (by referencing it from a test object, or generating against it).
- AI reads the issue and drafts test cases mapped to your project's template — titles, steps, expected results.
- Review the drafts, edit as needed, and save the ones worth keeping.
- The saved cases reference the Jira issue, so coverage traces back to the ticket.
04What it does and does not do
- Does: reference Jira issues from test cases/runs/sessions, and generate test cases from an issue.
- Does not: post results or comments back into Jira — the connection is read-and-reference, not two-way sync.
Generation returns reviewable drafts, not auto-created cases. See AI test case generation for the general flow.
05Related
06Frequently asked questions
How does TestOrchestrator connect to Jira?
Jira Cloud connects as an integration source using your Atlassian account email plus an API token, configured by an admin in Admin → External References. See the Jira integration docs for the exact steps.
Does it generate test cases from a Jira issue?
Yes. Point the AI generator at a Jira issue and it drafts test cases mapped to your project template. The drafts are reviewable — you choose which to save.
Can I link existing test cases to Jira issues too?
Yes. Beyond generation, you can reference a Jira issue from any test case, run, or exploratory session, so coverage traces back to the work item.
Does it sync results back into Jira?
No. The Jira connection is used to reference issues and to generate cases from them. It does not write results back into Jira.