Jira
Connect Atlassian Jira so the Sazabi agent can file issues into your Jira site.
Supported capabilities
- MCP connector: Atlassian — Give the Sazabi agent tools to search and manage Jira, Confluence, Jira Service Management, Compass, and Bitbucket from your workflow.
- Core integration: Jira — Connect Atlassian Jira so the Sazabi agent can file issues into your Jira site.
Each connection method has its own setup and permissions. Connecting one method does not enable the others.
Core integration
About
Connecting Jira lets the Sazabi agent create issues in your Atlassian Jira site, turning an investigation into a tracked ticket. Jira is an issue tracker integration.
The connection uses Atlassian OAuth and acts on behalf of the person who authorized it — Atlassian attributes every write to that user, so a dedicated service account is a good choice for the authorizing identity.
Jira is also available through the Atlassian MCP connector — a separate way to give the agent Jira tools.
Prerequisites
- An Atlassian account with access to the Jira site you want to connect.
- Organization admin access in Sazabi.
Set up in the dashboard
Open the Jira integration
In the dashboard, go to Settings > Integrations > Jira.
Authorize with Atlassian
Start the connection. Sazabi redirects you to Atlassian to authorize access to Jira; approve it, and Atlassian redirects you back. If you can access more than one Atlassian site, choose the site to connect.
Authorize with a dedicated service account where possible — Jira attributes every issue Sazabi files to the authorizing user.
Set up with the CLI
You can also start the Jira connection with the Sazabi CLI (installed and authenticated — see CLI reference).
Jira connects through an Atlassian OAuth browser flow — the CLI has no --credentials for it. Run:
sazabi integrations connect jiraThe command opens Atlassian's authorization in your browser (sign in to the dashboard as the same user), then waits for you to approve and pick the Jira site. --json changes only the output: the command still opens the browser and waits for the flow to finish, then prints the resulting connection as JSON:
sazabi integrations connect jira --jsonAuthorize with a dedicated service account where possible — Jira attributes every issue Sazabi files to the authorizing user. Run sazabi integrations list to confirm the connection.
Tasks
During an investigation the Sazabi agent can create a Jira issue and keep it current — updating fields, transitioning it through your project's workflow, commenting on it, and linking it back to the Sazabi issue or thread — so the ticket lands in the tracker your team already uses.
Verify
Open Settings > Integrations > Jira and confirm the connection reads connected for your Jira site. Then ask the agent, in a thread, to file a test issue into Jira, and confirm it appears in your Jira project. Delete the test issue in Jira afterward.
Troubleshooting
Connection shows needs attention — Open the affected connection in Settings > Integrations > Jira. If the authorizing account lost access to the site or projects, restore its permissions in Atlassian, then choose Check connection in Sazabi. If the authorization expired or was revoked, note the connection's project settings, choose Disconnect, then add the Jira connection again. Select the same site and restore its project settings. Adding a connection alone does not repair an existing multi-site connection.
Wrong site connected — Open the affected connection, choose Disconnect, then add a Jira connection and select the intended site during authorization.