|
Actions define how and when to create or update a ticket based on the content of an incoming email message. When defining actions, you can use data points from the incoming email message, information in JIRA, and information in lookup tables to determine which actions to take and what values to use. |
In the Name your action section, enter a name that indicates what the action will do.
For example, update-priority
.
If you do not define any conditions, this action will be applied to every incoming email that matches the handler.
The action criteria are evaluated in order. If the email does not match a condition, the add-on stops evaluating the criteria and does not perform the action. You can reorder the conditions by dragging the terms. |
If the action will update an existing ticket, enter search criteria to find the ticket.
Field | Description |
---|---|
Search Field | JIRA field to look in when searching for the ticket. |
Search Match Type | Whether the value in the search field Equals or Contains the search value. |
Search Value | Value to look for in the JIRA field. Enter a static value, or type { to select from the list of data points for this handler. |
Searcher | User account to use when performing the search. |
Add the fields that you want to define by clicking Add Issue Field and then selecting the field name.
If this action creates a new ticket, you must specify values for every field that JIRA requires for new tickets. To get you started, the add-on automatically adds the required fields and you cannot delete them. |
If score ranges are enabled for this handler, you can configure actions based on how many of the other actions are performed for an email and how important those actions are. For example, suppose this handler evaluates web form submissions for users who want to launch new applications. You may want to create a ticket for an additional review step based on how many special requests the user makes.
To enable score ranges, configure the Mail Handler settings. |
ScoreRange Greater Than 10
.Configure the action type and define how you want to populate JIRA tickets as you would for a standard action.
The add-on always evaluates score range actions after all other actions are evaluated. |