Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Note

The size limit of the emails received through an Email integration is 2 16 MB. If the overall size (content and attachments) exceeds 2MB16 MB, Jira Service Management ignores the email and doesn’t create an alert.

...

Expand
titleIgnore action

Some emails may contain no useful information. Ignore action allows discarding the emails that match the defined filter. For example, you can configure the action to discard all emails that contain the string "test" in the email subject.

Expand
titleCreate alert action

Create alert action creates an alert in Jira Service Management if the email passes the defined filter. As stated in the basic configuration, the default configuration uses email subject as the alert message and body as the description. Create alert action allows customizing how the email is processed. String utilities can extract information from the email and populate alert fields.

Create alert action configuration has several fields that you can modify. Jira Service Management makes the email information (from name, subject, etc.) available as tags, and UI supports dragging these tags into alert fields. The values for these tags are specified directly or extracted from the email variables.

  • The Message field contains the alert text.

  • The Alias field is a special alert field that plays a critical role in alert processing, and can be thought as a user-defined unique identifier for open alerts in Jira Service Management. There can be only 1 open alert with the same alias in Jira Service Management. This allows Jira Service Management to 1) deduplicate the same/similar alerts 2) identify alerts, and therefore it is setting the alias field properly is essential to be able to update existing alerts (acknowledge, add note, close and so on).

  • The Teams field indicates which team should be notified of alerts. When a team is defined in this field, Jira Service Management uses its escalation to determine the users to be notified.

  • Entity is the name of the entity to which the alert is related, name of the server, application, etc.

  • Source indicates where the alert originated from, typically the name of the monitoring tool or the From address of the email.

  • Tags are labels used for easier identification and categorization of alerts. Use commas in between for multiple tags.

  • Actions: The list of actions a recipient can execute to respond to an alert. Use commas in between multiple actions.

  • Description: Detailed description of the alert; anything that may not have fit in the Message field can be entered here.

  • Extra Properties: Additional alert properties. Enter the property's name in the first field and the value in the second.

  • Note is additional text message added to the alert when an alert is created.

  • User: Owner of the notes which are added to the alert.

...