JIRA for Crashes - API Documentation
Ⓔ Enterprise Only
This feature is available exclusively in Countly Enterprise.
Overview
JIRA for Crashes connects Countly crash groups with Atlassian JIRA issues using OAuth 1.0a. It supports creating issues from crash groups and synchronizing status between Countly and JIRA.
Quick Links
| Endpoint | Purpose |
|---|---|
| Login | Start OAuth login flow with JIRA |
| Callback | Complete OAuth callback and store access token |
| Check Login | Verify stored JIRA credentials |
| List | List crashgroup-to-JIRA issue mappings |
| Create | Create JIRA issue for a crash group |
| Sync | Synchronize Countly and JIRA issue status |
Database Collections
| Collection | Purpose |
|---|---|
countly.crashes_jira | Global OAuth token metadata (_id: "meta") |
countly.crashes_jira{appId} | Per-app crashgroup ↔ JIRA issue mappings |
countly.app_crashgroups{appId} | Crash status fields used in sync flow |
countly.apps | App-level crashes-jira settings |
Configuration & Settings
Global settings (scope: crashes-jira):
api_url: JIRA base URLapi_consumer_key: OAuth consumer keyclient_private_key: OAuth RSA private keycallback_url: Countly API base URL used for callbacklogin-to-jira: UI/login helper setting
App settings (under app.plugins["crashes-jira"]):
project: JIRA project key for issue creationtype: JIRA issue typetodo-states: JIRA states treated as unresolveddoing-states: JIRA states treated as resolvingdone-states: JIRA states treated as resolved
Workflows
OAuth setup
- Open Login to authorize Countly in JIRA.
- JIRA redirects to Callback.
- Validate setup with Check Login.
Issue lifecycle
Notes
- Sync logic is also triggered internally when crash resolve/unresolve actions run.
- App lifecycle hooks clear mappings on app delete/reset/clear-all.
Ⓔ Enterprise
This feature is part of Countly Enterprise.
Get Access:
Already a Customer? Use support portal if you have any questions
Last Updated: 2026-02-15