Page your on-call team the moment someone files an urgent Jira work item, for example a customer request in Jira Service Management. A Jira Automation flow creates the incident through the Incidents API, and two more flows acknowledge and resolve it as the work item moves.
The flows store the incident's ID and link on the work item.
incident_id and associate it with all screens.BU_incident_url.Add a Send web request action. Set Web request URL to https://incidents.betterstack.com/api/v2/incidents, HTTP method to POST and Web request body to Custom data:
Replace {ESCALATION_POLICY_ID} with the ID of the escalation policy to page. Add an Authorization header with your API token:
Check Delay execution of subsequent rule actions.
Add an Edit work item action. Set incident_id to {{webResponse.body.data.id}} and BU_incident_url to https://incidents.betterstack.com/team/YOUR_TEAM_ID/incidents/{{webResponse.body.data.id}}, with your team's ID from its Better Stack URL.
Click Save and enable.
Every new work item that matches your condition now creates a Better Stack incident.
These flows act on the incidents the flow above created, through the incident_id field. Work items Better Stack created get Acknowledge and Resolve buttons from Better Stack for Jira instead.
In Progress and click Save.incident_id is not empty.Add a Send web request action. Set Web request URL to https://incidents.betterstack.com/api/v2/incidents/{{incident_id}}/acknowledge, HTTP method to POST, the same Authorization header as above, and Web request body to Custom data:
Click Save and enable.
Repeat for resolving: To status Done, a Web request URL ending in /resolve, and this body:
Moving a work item to In Progress now acknowledges its incident, and moving it to Done resolves it.
Please let us know at hello@betterstack.com.
We're happy to help! π
We use cookies to authenticate users, improve the product user experience, and for personalized ads. Learn more.