Skip to main content

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.

EndpointPurpose
LoginStart OAuth login flow with JIRA
CallbackComplete OAuth callback and store access token
Check LoginVerify stored JIRA credentials
ListList crashgroup-to-JIRA issue mappings
CreateCreate JIRA issue for a crash group
SyncSynchronize Countly and JIRA issue status

Database Collections

CollectionPurpose
countly.crashes_jiraGlobal 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.appsApp-level crashes-jira settings

Configuration & Settings

Global settings (scope: crashes-jira):

  • api_url: JIRA base URL
  • api_consumer_key: OAuth consumer key
  • client_private_key: OAuth RSA private key
  • callback_url: Countly API base URL used for callback
  • login-to-jira: UI/login helper setting

App settings (under app.plugins["crashes-jira"]):

  • project: JIRA project key for issue creation
  • type: JIRA issue type
  • todo-states: JIRA states treated as unresolved
  • doing-states: JIRA states treated as resolving
  • done-states: JIRA states treated as resolved

Workflows

OAuth setup

  1. Open Login to authorize Countly in JIRA.
  2. JIRA redirects to Callback.
  3. Validate setup with Check Login.

Issue lifecycle

  1. Create mapping via Create.
  2. Read mapping via List.
  3. Keep statuses aligned via Sync.

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