Skip to main content

List crash JIRA issues

Endpoint

/o?method=crashes-jira

Enterprise Only
This API is available exclusively in Countly Enterprise.

Overview

Returns JIRA issue mappings for one or more crash groups and adds a computed JIRA browse URL.

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: Read on the crashes feature

Request Parameters

ParameterTypeRequiredDescription
methodStringYesMust be crashes-jira
app_idStringYesApplication identifier
crashgroup_idStringNoSingle crash group ID
crashgroupsArray/StringNoArray of crash group IDs
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

[
{
"_id": "65c5f2782c5f5300121a00c1",
"issue": {
"key": "MOB-1234"
},
"created": 1739629012,
"lastChecked": 1739630010,
"url": "https://jira.example.com/browse/MOB-1234"
}
]

Response Fields

FieldTypeDescription
_idStringCrash group ID
issueObjectStored JIRA issue metadata
issue.keyStringJIRA issue key
createdNumberMapping creation timestamp (unix seconds)
lastCheckedNumberLast sync check timestamp (unix seconds)
urlStringComputed JIRA browse URL (api_url + /browse/<key>)

Error Responses

HTTP StatusResponse
401{ "result": "User does not exist" } or auth validation message

Behavior/Processing

  • Requires Read permission on the crashes feature.
  • Reads the plugin configuration and uses crashes-jira.api_url to build returned JIRA browse links.
  • Builds the crash group list from crashgroups when provided; otherwise uses a single-element list containing crashgroup_id.
  • Queries crashes_jira{app_id} for documents whose _id is in that crash group list.
  • Adds url to each returned mapping as <api_url>/browse/<issue.key>.
  • The handler does not currently return a custom error body for database read failures in this branch.

Database Collections

CollectionUsed forData touched by this endpoint
countly.crashes_jira{app_id}Endpoint data sourceStores endpoint-related records this endpoint reads or modifies.

Examples

Example 1: List one crash group's issue mapping

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

Example 2: List mappings for multiple crash groups

/o?method=crashes-jira&app_id=5f9c8a3b4d1e2a001f3b4567&crashgroups[]=65c5f2782c5f5300121a00c1&crashgroups[]=65c5f27f2c5f5300121a00c2&api_key=YOUR_API_KEY

Ⓔ Enterprise

This feature is part of Countly Enterprise.

Get Access:

Already a Customer? Use support portal if you have any questions


Last Updated

2026-04-18