How to allow JSM Cloud Operations Sync to filter Alert actions based on custom fields or JQLs
Platform Notice: Cloud - This article applies to Atlassian products on the cloud platform.
Summary
Currently, we have the following feature request to allow our JSM integration Sync integration with Operations to allow custom fields as a filter to the Alert actions:
- OPSGENIE-338 - Getting issue details... STATUS
This article provides a workaround using Operations Sync and Jira Webhooks to add a JQL (which can consider custom fields) as a filter for the Alert actions.
Important note
This solution is only available for customers with JSM Premium or Enterprise offerings, as modifying Alert actions is only available for those licenses.
Solution
As a workaround for the feature request, you can create a sync using the Different Site option, but you're not actually using a different site—you're essentially calling back into your JSM site.
Create the Sync:
Go to your team’s operations page
On the left navigation panel, select Sync and then Create sync
Under Choose your project's Jira site select Different Jira Site
Give the Sync a Name
Select the appropriate Assignee Team
Select Service for the Project Type
Make a copy of the URL listed in the Steps to configure the sync box
Configure your Alert Rules - Make sure they'll match the Webhook events being sent from Jira (for example jira:issue_updated and/or jira:issue_created)
Click Turn on Sync
Create the Webhook in Jira:
In Jira navigate to Settings -> System -> Webhooks
Click Create Webhook
Give it a name
Supply the URL copied from the Sync creation steps above
Under Issue Related Events, supply your JQL that includes your custom field
Under Issue, check the created and updated boxes
Click Create Webhook
The above steps should generate alerts in the appropriate team based on the JQL.