Jira

OpenSRE connects to Jira to create incident tickets, update existing issues, and add investigation findings as comments — keeping your team’s workflow in sync with automated investigations.

Prerequisites

Jira Cloud account (Jira Server/Data Center also supported)
API token and project access

Setup

Option 1: Interactive CLI

opensre integrations setup

Select Jira when prompted and provide your base URL, email, API token, and project key.

Option 2: Persistent store

Add to ~/.opensre/integrations.json:

{
  "version": 1,
  "integrations": [
    {
      "id": "jira-prod",
      "service": "jira",
      "status": "active",
      "credentials": {
        "base_url": "https://your-org.atlassian.net",
        "email": "you@example.com",
        "api_token": "your-api-token",
        "project_key": "OPS"
      }
    }
  ]
}

Field	Description
`base_url`	Required. Your Jira instance URL (e.g., `https://your-org.atlassian.net`)
`email`	Required. Email address associated with the API token
`api_token`	Required. Jira API token
`project_key`	Required. Default project key for new issues (e.g., `OPS`, `SRE`)

Creating a Jira API token

Go to id.atlassian.com/manage-profile/security/api-tokens
Click Create API token
Give it a label (e.g., opensre)
Copy the token

For Jira Data Center/Server, use a personal access token from Profile → Personal Access Tokens instead.

Verify

opensre integrations verify jira

Expected output on success:

Service: jira
Status:  passed
Detail:  Configured for Jira at https://your-org.atlassian.net.

This is a configuration-presence check (base_url, email, and api_token are all set) rather than a live API call.

Troubleshooting

Symptom	Fix
401 Unauthorized	Check email and API token combination
404 Not Found	Verify `base_url` (include `https://`) and `project_key`
403 Forbidden	The user may lack permission to create issues in the project

Security best practices

Use a dedicated Jira user for OpenSRE with only the permissions it needs (create and comment on issues).
Store credentials in ~/.opensre/integrations.json, not in source code or environment variables.
Rotate the API token periodically.

Overview

LLM providers

Observability and incidents

Cloud, code, and collaboration

Messaging

Data and workflow systems

Prerequisites

Setup

Option 1: Interactive CLI

Option 2: Persistent store

Creating a Jira API token

Verify

Troubleshooting

Security best practices

​Prerequisites

​Setup

​Option 1: Interactive CLI

​Option 2: Persistent store

​Creating a Jira API token

​Verify

​Troubleshooting

​Security best practices

Prerequisites

Setup

Option 1: Interactive CLI

Option 2: Persistent store

Creating a Jira API token

Verify

Troubleshooting

Security best practices