Jira

Turn issues from your project’s Issues tab into Jira tickets. Each ticket carries the issue’s description, expected vs actual behavior, reproduction steps, severity-mapped priority, a screenshot link, and a link back to the TesterArmy issue.

How the connection works

Jira connects once per project: a teammate authorizes TesterArmy for your Atlassian account and every project member can export tickets from then on, no individual sign-in required. TesterArmy never stores Jira credentials - the OAuth connection is managed by our auth provider and only requests issue read and write access plus user profile read for the assignee picker.

Atlassian has no app identity for this kind of connection, so tickets are created through the account that connected Jira; each ticket names the teammate who exported it in the description. The project stores two settings: the default Jira project and the default issue type new tickets are created with.

If the authorized account can reach several Jira sites, the first one is used. Connecting a different site means authorizing with an account whose first site is the one you want; a site picker is planned.

Setup

1. Go to Project → Settings → Integrations → Jira and click Connect Jira.
2. Approve TesterArmy for your Atlassian account. Anyone on the project can do this; the connection is shared.
3. Back in TesterArmy, pick the default Jira project and issue type tickets should be created with and save them. These are shared by the whole project, so they only need to be set once.

Creating tickets

1. Open an issue from the project’s Issues tab.
2. Click Create ticket in the issue header. With both Linear and Jira connected, the button becomes a menu - pick Jira.
3. Adjust the ticket in the dialog: title, Jira project, issue type, priority, assignee, and due date. Fields that are not on the Jira project’s create screen are hidden automatically.
4. The ticket key (for example ENG-42) appears in the header and links to Jira.

Each issue links to at most one ticket - exporting again is prevented, and the existing ticket is surfaced instead. Severity maps to Jira priority by name: severity 5 becomes Highest, 4 High, 3 Medium, 2 Low, and 1 Lowest; sites with custom priority schemes default to the middle priority of the scheme, and you can always pick another in the dialog.

Jira projects whose create screen requires custom fields TesterArmy does not collect cannot be exported to yet - pick a different Jira project or make those fields optional.

Disconnecting

Disconnect Jira in the project’s integration settings unlinks the project and removes the stored connection once no other project uses it. Already-created tickets are unaffected. You can also revoke TesterArmy from your Atlassian account settings at any time; exports will fail until the project reconnects.