Overview
Send Jira issues to Callgoose SQIBS. A Jira webhook posts issue created and updated events to your SQIBS API endpoint. SQIBS opens an incident for the issues you choose, for example high priority bugs, and resolves it when the issue is resolved as Done.
How it works
Done closes it.Want SQIBS to fix known issues before anyone is paged? See Fix known issues automatically.
Step 1: Add the API filter in SQIBS
- In SQIBS, open Services, choose the service that should receive these incidents, and click Add Or Update API Integration.
- In Select Integration Template, choose Jira. It fills in these filter values:
| Part | Payload JSON key | Key value contains | What it does |
|---|---|---|---|
| Trigger | "issue"."fields"."priority" |
(anything) | Opens an incident. |
| Resolve | "issue"."fields"."resolution"."name" |
done |
Resolves the open incident. |
| Match | "issue"."id" |
Ties the resolve message to the incident it opened. | |
| Title from | "issue"."fields"."summary" |
Becomes the incident title. |
- Choose the Priority for these incidents and click Save.
The template's trigger has no value, so every issue with a priority (almost all of them) opens an incident. Change the trigger key to "issue"."fields"."priority"."name" and set Key value contains to the priority you page on, for example Highest. Also narrow the webhook with JQL in step 2.
The template is a starting point, not a lock-in: every value stays visible and you can change it.
In the API Integration window, click the round
{} button at the bottom right. Paste a payload that SQIBS received (copy it from the API log). SQIBS lists every key with its value, each with a copy button. Copy the key into Payload JSON key and the value into Key value contains. No need to read the JSON by hand.Step 2: Create a webhook in Jira
- In Jira, go to Settings > System > WebHooks and click Create a WebHook.
- Set Name to
CallgooseSQIBSand URL to your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=jira&token=<your-token>
Replace <your-endpoint> and <your-token> with the values from your SQIBS account. See how to get the endpoint URL and API tokens.
- Under Issue related events, enter a JQL filter for the issues you want, for example
project = OPS AND type = Bug, and tick Issue: created and Issue: updated. - Click Create.
Step 3: Test it
The API log saves payloads only while API Tracking is on for the token. Turn it on under API Tokens before you test; it switches itself off after 48 hours.
- Create an issue that matches the JQL and has the priority you chose.
- In SQIBS, a new incident opens, titled with the issue summary. Jira's payload looks like this (shortened):
{
"webhookEvent": "jira:issue_created",
"issue": {
"id": "10042",
"key": "OPS-42",
"fields": {
"summary": "Checkout fails for EU customers",
"priority": {
"name": "Highest"
},
"resolution": null,
"status": {
"name": "To Do"
}
}
}
}
- Resolve the issue as Done. Jira sends an update with
"resolution": {"name": "Done"}for the same issue id, and SQIBS resolves the incident.
No incident? Open the API log (with API Tracking on). If the payload is there, the filter did not match it: paste it into the JSON key creator and check the keys. If it is not there, check the URL and token in the Jira webhook.
Fix known issues automatically
Many alerts have a known fix: restart a service, clear a full disk, run a health check. SQIBS can run that fix for you the moment the incident opens. This is event-driven auto remediation. For example, when a Highest priority issue is raised against a service, SQIBS can run a workflow that collects that service's health and recent logs for the on-call engineer.
Safe by design. SQIBS runs only workflows your own engineers wrote and approved for your environment. Nothing is guessed or generated: the same steps an engineer would run by hand, run sooner. If the workflow does not fix the issue, the engineer is paged as usual.
To set it up, in the same API filter:
- Select Workflow: choose the automation workflow to run when this filter opens an incident.
- If success then make incident resolved: turn on to resolve the incident when the workflow succeeds.
- Waiting time for escalate to escalation policies: how many minutes to give the workflow before paging the on-call engineer.
Start with low-risk workflows, such as a health check, and add fixes as you come to trust them.
Learn more:
- Prometheus: incident auto remediation, a full worked example.
- Automation workflow: build a workflow from actions.
- Run workflows where your systems are: SSH, Bash, PowerShell, Python, Ansible, kubectl, Terraform.