Jira

Connect Jira to your team, set a default Jira project per Operio project, and your team can file bugs directly from failed test case runs.

What the Jira integration does

From a failed test case result, the Report Bug button creates a Jira Bug issue pre-filled with run context:

• A summary line with the environment, test case name, and a short failure reason
• A link back to the Operio test run
• Test case name and environment details
• Execution timestamp and duration
• Reporter name
• The share link, if sharing is enabled for the run
• Expected vs actual behavior
• Steps to reproduce, taken from the run's bug report or the test case steps
• Error details, when available

After creation, Operio shows the new issue key with a link to open it in Jira.

Connect Jira to your team

1. Open Settings → Integrations in the project sidebar.
2. Find Jira and click Connect.
3. Complete the Atlassian OAuth flow and authorize Operio.
4. You're redirected back to Operio, and the card shows Connected with your Jira site name.

The connection is shared across all projects in the team, so this only needs to happen once.

OAuth scopes

Operio requests these Atlassian scopes:

• read:jira-work and write:jira-work to read projects and create issues
• read:jira-user to identify the connected user
• offline_access for refresh tokens and long-lived access

Configure a default Jira project

After connecting at the team level, each project needs a default Jira project:

1. On the Jira integration card, click Configure.
2. Select a Jira project from the list.
3. Click Save.

Bug reports from this Operio project land in the selected Jira project. Without one configured, Report Bug prompts you to set it up in Settings → Integrations.

Report a bug from a failed run

1. Open a failed test case result from Runs or the test case results history.
2. Click Report Bug in the run header.
3. Confirm the target Jira project shown in the dialog.
4. Click Report Bug to create the issue.

The button only appears when the run has finished and its status is failed.

One thing to watch: Operio doesn't deduplicate reports. Clicking Report Bug again on the same run creates another Jira issue, so check the linked issue key before re-reporting.

Issue content

Issues are created with type Bug, and the description is structured in sections:

Summary

A one-line title with the environment (when available), test case name, and a short failure reason.

Operio Run

A bullet list with the test run link, test case name, environment, execution time, reporter, and the share link if there is one.

Expected vs Actual

Filled from the run's bug report when present, otherwise derived from the test case's verify steps and error output.

Steps to Reproduce

Ordered steps from the bug report, or reconstructed from the test case steps, including the initial navigation to the environment's base URL.

Error Details

The full error output in a code block, when the run captured one.

Disconnect Jira

1. Open Settings → Integrations.
2. On the Jira card, click Disconnect.

This removes the team-level connection. Report Bug stays unavailable until Jira is reconnected and a default project is configured again.

Troubleshooting

Multiple Atlassian sites

If your Atlassian account has access to more than one Jira site, Operio connects to the first site you authorize during the OAuth flow. To target a different site, disconnect Jira, reconnect, and grant access to only the site you want Operio to use.

Related

• Integrations overview
• Viewing Results
• Sharing Results, since share links can appear in Jira issue descriptions