Jira Service Management integration custom field

wes.saunders

Hello, when an Alert is created in Opsgenie, I've set up the integration to create a Jira Service Management Issue. However, I'm having trouble populating an Issue's custom field named Category.

I've tried each of these without success.

Ideally, I'd like to populate this field with a constant value, i.e. Category=Foo. Is this possible?

Finally, which one of these should I configure, and does the order matter?

Nick Haller

Hi @wes.saunders ! 

Realistically it would depend how this custom field is parsing in the payload, but we typically see one these options working fairly consistently:

• {{_payload.issue.fields.customfield_13154.value}}

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

  • ^ Where this pulls the string between value= and ,

To see how this custom field parses in the payload, you may want to 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' Description - since it can parse up to 15k characters.

 

As for which one of those Create Alert actions you should configure, you can configure or edit any one of them. That also would depend on what your use-case is, and which issues should (or should not) create Opsgenie alerts. By default we offer those three actions because they meet most standard workflows, and create Opsgenie alerts for when new JSM issues are created - depending on their status, webhook event, etc.

Order of those actions does matter too! Opsgenie will evaluate them from top >> down, and when an action's filter/conditions are met, execute the action.

 

Hope this helps! Let us know if you have any other questions, issues, etc. If you'd like to also test with the {{_payload}} suggestion above, and share a screenshot of the alert following with the custom field, we could provide further suggestions.