Jira
Automatically create Jira issues when incidents are opened, synchronize status transitions, and mirror timeline comments between Batida and Jira.
Setup
- Go to Settings > Integrations > Jira in the Batida dashboard.
- Enter your Jira site URL (e.g.,
https://your-team.atlassian.net). - Generate an API token from Atlassian account settings.
- Enter the API token along with your Jira email address.
- Select the default project and issue type (Bug, Task, or Incident).
- Click Save & Verify.
Site URL: https://your-team.atlassian.net
Email: you@company.com
API Token: ATATT3xFfGF0...API token vs password
Atlassian no longer accepts passwords for API authentication. You must use an API token generated from your Atlassian account.
Auto-create issues
When an incident is opened in Batida, a Jira issue is automatically created with the following mapping:
| Batida field | Jira field |
|---|---|
| Incident title | Issue summary |
| Description | Issue description |
| Severity | Priority (critical = Highest, high = High, ...) |
| Assigned responder | Assignee (matched by email) |
| Team | Project component or label |
The Jira issue key (e.g., OPS-142) is stored on the incident record and displayed in the Batida UI.
Status synchronization
Status transitions are synced bidirectionally:
Batida to Jira: When an incident status changes in Batida (investigating, identified, monitoring, resolved), the Jira issue transitions through a configured workflow. Default mapping:
Batida status Jira transition Opened To Do -> In Progress Identified In Progress -> In Review Resolved In Review -> Done Jira to Batida: When a Jira issue is transitioned to Done, the linked incident in Batida is automatically marked as resolved.
Custom workflow mapping
You can customize the status mapping under Settings > Integrations > Jira > Workflow Mapping to match your Jira project's workflow states.
Timeline comments
Every comment added to the incident timeline in Batida is posted as a comment on the linked Jira issue. The comment includes the author's name, timestamp, and the comment body.
Troubleshooting
- "Invalid authentication": Verify your API token and email. Regenerate the token if needed.
- Issues not created: Check that the selected project key is valid and the issue type exists in that project.
- Status sync not working: Confirm the workflow transition names match your Jira project configuration. Use the workflow mapping screen to adjust.