Jira Cloud Alert Source
Get alerts from Jira Cloud into Squadcast
Last updated
Get alerts from Jira Cloud into Squadcast
Last updated
Follow the steps below to configure a service so as to push related alert data from Jira onto Squadcast.
Squadcast will then process this information to create incidents for this service as per your preferences.
Pre-requisites
A valid Squadcast cloud / On-Premise subscription
A user account in JIRA Cloud with Administrator privileges
Navigate to Services -> Service Overview -> select or search for your Service. Expand the accordion -> In the Alert Sources section, click Add.
2. Select Jira Cloud. Copy the displayed Webhook URL to configure it within Jira Cloud. Finish by clicking Add Alert Source -> Done.
Important:
When an alert source turns Active, it’ll show up under Configured Alert Sources, you can either generate a test alert from the integration or wait for a real-time alert to be generated by the Alert Source. An Alert Source is active if there is a recorded incident via that Alert Source for the Service.
Login to Jira Cloud and go to Settings in left-side pannel.
2.Go to System under Jira Settings
3.Click on the WebHook tab under the Advanced Section.
4.Click on Create a Webhook.
5. Paste the Jira Cloud Webhook URL copied from Squadcast Dashboard in the URL field and check the created And updated check boxes under issues. Click on Create to finally save the webhook.
Important:
If you are using both Jira as an alert source and Jira Cloud extension, sometimes it might cause duplicate ticket/incident loops depending on your configuration. In order to prevent that, please add this condition reporter.displayName != "Squadcast" to your JQL query configuration under your Jira Webhook configuration for Squadcast alert source.
Note
Enable only the highlighted Issue related events as shown in the screenshot above. Squadcast will ignore any other Issue event type.
Now whenever an issue goes to status-category with key new in Jira, an incident will be triggered in Squadcast. Also when that issue goes to status-category with key done in Jira, it will be resolved in Squadcast.
