Jira

Reelspect connects to Jira Cloud so you can link Jira issues to your tests and create issues from failed results. An organization Admin sets up the connection once for the organization and maps each Reelspect project to a Jira project.

Reelspect never creates or links Jira issues by itself, for example when a test fails. Every issue comes from someone selecting Create Issue or + Link Issue.

Connecting Jira

Open Settings in the organization sidebar and select the Integrations tab. Only organization Admins can manage integrations.

Adding a connection

A connection is one Jira Cloud site (for example https://your-company.atlassian.net), accessed with one Jira account’s API token and that account’s email. Generate the token on the Atlassian API tokens page (linked under the field). When editing a connection, leave the token empty to keep the current one.

Issues that Reelspect creates are created by this Jira account, so it needs permission to browse and create issues in the mapped Jira projects.

The check icon on a connection tests it. Deleting a connection also removes all its project mappings; issue links already on test cases stay.

Mapping projects

A project needs a mapping before its members can search, link or create issues. Select + Mapping (available once a connection exists) and choose the connection, the Reelspect project and the Jira project.

Each Reelspect project maps to one Jira project. Issue type and field mapping are not available yet. Removing a mapping stops the project from searching and linking Jira issues; existing links stay.

Linking issues

Once the project is mapped, Jira issues can be linked to:

Library test cases (Tester or Manager)
Test plans and runs (Tester or Manager)
Individual results in a run (Tester or Manager)
Your own Sandbox test cases (any role)

Search by issue key or words from the summary; up to 20 matches are shown. Select a linked issue’s badge to open it in Jira, or hover over it to see its type, status, priority, summary, description, reporter and assignee (read from Jira at that moment) and to Unlink it.

If the dialog says Jira is not configured for this project., ask an organization Admin to add a connection and a mapping.

Reporting an issue from a result

When a result is Failed or Error and the project is mapped to Jira, the result details show Report Issue:

Field	Description
`Summary`	Pre-filled with the test case title followed by `- Test Failed`. Up to 500 characters.
`Issue Type`	`Bug` (default), `Task`, `Story` or `Epic`. The type must exist in the mapped Jira project.
`Priority`	`None`, `Highest`, `High`, `Medium` (default), `Low` or `Lowest`.
`Description`	Pre-filled with the environment (URL and device), the agent’s expected behaviour, actual behaviour, failure reason and steps to reproduce, and a link to the session recording. Up to 5,000 characters.

Create Issue creates the issue in the mapped Jira project and links it to both the result and the Library test case. Reporting an issue needs the Tester or Manager role.