-
Suggestion
-
Resolution: Unresolved
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.
- relates to
-
OPSGENIE-651 As an admin, I want to use regex or any way on the Filter of Action Filter of an integration to configure the filter with non-predefined fields
- Reviewing
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
Form Name |
---|
We at Omnissa are a customer and are also experience this issue. Would be lovely to see it happen!