Uploaded image for project: 'Opsgenie'
  1. Opsgenie
  2. OPSGENIE-338

Ability to filter on Jira/JSM custom fields in create alert actions

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Description

      At this time, Jira and JSM integrations can only filter on default fields in the create alert actions. Having the ability to also filter on custom fields in the new framework would add additional flexibility.

      Workaround

      Custom fields can still be extracted from the Jira / JSM payload, typically with something like:

      {{_payload.issue.fields.customfield_12345.value}}
      
      {{_payload.issue.fields.customfield_12345.substringBetween("value=",",")}}

      To see how a custom field parses in the payload, add:

      {{_payload}}

      to the create alert action's Description field. Sometimes the payload will be truncated in the Logs, but should parse entirely in the alert's Description - since it can parse up to 15k characters.

      String processing and regex can be helpful to extract data as well.

      Once you find the dynamic field that extracts the custom field, parse this into one of the create alert action's alert fields - such as an extra property.

      You can then use Alert policies to filter on the extra property, and modify the alert to add a responder, add a tag, etc.

       

            [OPSGENIE-338] Ability to filter on Jira/JSM custom fields in create alert actions

            No work has yet been logged on this issue.

              36bd3fea80e3 Makarand Gomashe
              nhaller Nick Haller
              Votes:
              120 Vote for this issue
              Watchers:
              75 Start watching this issue

                Created:
                Updated: