Skip to main content

Sync crash and JIRA status

Endpoint​

/i/crashes-jira?method=sync

Ⓔ Enterprise Only
This API is available exclusively in Countly Enterprise.

Overview​

Synchronizes status between Countly crash groups and mapped JIRA issues.

Authentication​

  • Authentication methods:
    • API Key (parameter): api_key=YOUR_API_KEY
    • Auth Token (parameter): auth_token=YOUR_AUTH_TOKEN
    • Auth Token (header): countly-token: YOUR_AUTH_TOKEN

Permissions​

  • Required permission: Update on the crashes feature

Request Parameters​

ParameterTypeRequiredDescription
methodStringYesMust be sync
app_idStringYesApplication identifier
crashgroup_idStringNoSpecific crash group to sync; if omitted, plugin attempts to sync all mapped groups
api_keyStringYes (or auth_token)API key authentication
auth_tokenStringYes (or api_key)Auth token authentication

Configuration Impact​

SettingDefaultAffectsUser-visible impact
crashes-jira.*Crashes Jira integration defaultsJira integration logic and synchronization behavior.Changes to Jira integration settings can alter authentication, sync behavior, and returned integration state.

Response​

Success Response​

Possible success responses for single-crash sync:

{
  "result": "Succesfully updated crash"
}
{
  "result": "Success"
}
{
  "result": "Crash is already in sync"
}

Response Fields​

FieldTypeDescription
resultStringSync operation status

Error Responses​

HTTP StatusResponse
404{ "result": "Failed to find crashgroup" }
404{ "result": "Failed to find crashgroup jira issue" }
500{ "result": "Failed to find app" }
500{ "result": "Incomplete jira-crashes app config" }
500{ "result": "Missing access token, please log in to JIRA" }
500{ "result": "Failed to find JIRA access token" }
500{ "result": "Ran into an error while connecting to JIRA" }
500{ "result": "Failed to update crashgroup" }
500{ "result": "Failed to get JIRA issue transitions" }
500{ "result": "Failed to transition JIRA issue" }
500{ "result": "Could not find transition" }

Behavior/Processing​

  • Compares Countly crash states (is_resolved, is_resolving) with JIRA issue status.
  • If JIRA status is newer, Countly crash group is updated.
  • If Countly status is newer, endpoint tries to transition JIRA issue.
  • Updates lastChecked timestamp in mapping document.

Database Collections​

CollectionUsed forData touched by this endpoint
countly.appsApp configuration and metadataStores app-level feature settings and metadata used or modified by this endpoint.
countly.app_crashgroups{app_id}Endpoint data sourceStores endpoint-related records this endpoint reads or modifies.
countly.crashes_jiraEndpoint data sourceStores endpoint-related records this endpoint reads or modifies.
countly.crashes_jira{app_id}Endpoint data sourceStores endpoint-related records this endpoint reads or modifies.

Examples​

Example 1: Sync one crash group​

/i/crashes-jira?method=sync&app_id=5f9c8a3b4d1e2a001f3b4567&crashgroup_id=65c5f2782c5f5300121a00c1&api_key=YOUR_API_KEY

Example 2: Trigger sync for all mapped crash groups​

/i/crashes-jira?method=sync&app_id=5f9c8a3b4d1e2a001f3b4567&api_key=YOUR_API_KEY

Limitations​

  • Single-crash sync gives deterministic response.
  • All-crashes sync is loop-based and may not return per-crash status details.

Ⓔ 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-16