Page Comparison

Overview

Jira Service Management parses your data to construct rich and informative alerts. You can use dynamic fields properties to customize alert properties your alerts and alert conditions.

Dynamic (draggable)

...

properties

Draggable fields properties bring significant data for creating and managing well-informed alerts. The integration framework provides different dynamic fields properties specific to the integrated application. You can use dynamic fields properties in the filters of your integration actions as well as alert fields. In the filter, fields dynamic properties are available to select in the condition drop-down. In the alert properties, you can drag a dynamic field property into any input alert field you find appropriate.

Jira Service Management interprets the expressions within the double-curly braces as dynamic fieldsproperties. Dynamic data populates at every notification that's sent to Jira Service Management. For example, someone creates an issue in Jira and enters "This is the summary" for the summary. Using Jira Service Management’s Jira integration, "[Jira] {{summary}}" for Message in a 'Create alert' Action creates an alert with the message "[Jira] This is the summary". It will then notify the users. All we needed to do is drag {{summary}} to the message. When the issue is created, Jira Service Management get gets notified automatically. It creates an alert with the issue's summary in the message.

You can mix static text with dynamic fieldsproperties. In the example above, the "[Jira] " in "[Jira] {{summary}}" is static and it'll be at the beginning of the message for every new alert. "{{summary}}" can be different for each alert.

Using raw parameters from webhook URL, payload, and headers

You can insert URL parameters or http payload parameters from webhooks directly into your alerts. For example, an integrated application sends a variable named timestamp to Jira Service Management in the webhook payload. But timestamp isn't available as a draggable field property in the configuration page. If you still need to use timestamp in your alerts, you can add {{_payload.timestamp}} to the input fieldsfield.

Nested payload variables are accessible as well. In the example, we could also use _payload.issue.fields.environment to access the following value that is in the http body of the webhook:

...

To control your alert fields further, you can use string processing methods on dynamic fieldsproperties. For example, an Integration has an 'Add Note' action, and Note is configured as "note: {{comment_body.substringAfter("is")}}".

Now when someone in the integrated application adds "This is the comment" as a comment to the issue, a note is added to the corresponding lertalert, with the text "note: the comment". Learn Read more about string processing methods.