Page Comparison

There are various strategies available out-of-the-box:

• Create Or Comment Issues: either create a new issue or comment on it. It supports Split Regex (see below)
• Create Or Comment Or Link Issues: either create a new issue or comment it if the issue matches the given JQL criteria, otherwise Create a new issue and link it. It supports Split Regex (see below).
• Always Add Comments: find a related issue for each email and if found, comment it. It supports Split Regex (see below)..
• Always Create Issues: create new issues for all incoming emails.
• Service Desk Create or Comment
• Create Issues or Email Log: No comments will be added.

Handler actions (available for all the above strategies):

• Executes workflow transition on

• issues: if enabled, the mail handler executes a workflow transition on the issue (read on for more details).

• Initializes Issue Fields: if enabled, the mail handler looks up a Field Context and applies its field rules to initialize issue fields.

• Overrides Default Issue Lookup: if enabled, the mail handler looks up a Field Contextand applies its issue lookup field rules to find the issue that can be associated with the incoming email.
• Filter incoming emails: If enabled, the mail handler looks up a Field Contextand applies its filtering rules to the email.
  

Event: An issue event that is fired for each incoming email that the mail handler processes.

Acknowledge New Issues

: If an email template is selected here, it will be used to generate auto-acknowledge emails when a new issue is created from an email.

Acknowledge New Comments

: If an email template is selected here, it will be used to generate auto-acknowledge emails when a new comment is added to an issue from an email.

Sender Email Address Field: The custom field selected here will be used to store the email address of the email's sender

Sender Name Field: The custom field selected here will be used to store the name of the email's sender

User Recipients

: This attribute determines how the mail handler should treat users recognized as recipient email addresses

:

• Add to watchers: save as watchers in the issue
• Save to multi-user picker field: save them in the selected user picker field
• Treat as email addresses: treat them as email addresses and save the email addresses in the recipient fields (see below)

Recipient field (To): The custom field selected here will be used to store email addresses of the email's TO recipients

Recipient field (Cc): The custom field selected here will be used to store email addresses of the email's CC recipients

Email Address Exclusion

: Email addresses (one per line) entered here are not saved in the sender or recipient fields (useful to save the mail handler address here to avoid mail loops). Supports regular expressions, to ensure your email address exclusion will not run into problems. Include (?i) at the beginning of the email address for safety.

Split Regex

: Regular expressions (one per line) entered here are used to split the email body by a delimiter (optionally the original incoming email as well). See more details below.

External Email Senders: Specify how to treat emails sent from email addresses not registered as users in Jira. Options are to accept the mails for processing or to ignore (leave in the mailbox) these emails. If you want to prevent the situation that practically anyone could pollute your Jira instance by sending emails, simply set this option to Ignore.

Jira Mail Strategy

: Specifies how to treat emails sent from the current or another Jira instance. Options are available to accept or ignore these emails.

Ignore Issue ID in Email Headers

: By default, Email This Issue checks for the "In-Reply-To" and "References" email headers for Jira IDs if no issue keys appear in the email subject. If such an issue ID is found, it comments the issue.

By enabling this option you can override the default behavior and make JETI ignore these email headers. It can be useful to prevent confusion when an email sent from Jira is replied or forwarded back to Jira. In such cases, the seemingly unrelated issues may be commented on. If this checkbox is turned on, JETI will only use the email subject and its own Issue Lookup Field Rules to process emails but will ignore the invisible email headers.