Versions Compared

Key

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

...

AttributeDescriptionRequired
ProjectProject to which the context applies. If left empty, context applies to all projects(error)
Issue TypeIssue Type to which the context applies. If left empty, context applies to all issue types(error)
Email Processing Strategy

Determines how Email This Issue Mail Handler processes the incoming emails.

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

  • Create Or Comment Issues: either create new issue or comment it. It supports Split Regex (see below)
  • Create Or Comment Or Link Issues: either create 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.

All strategies also do the following (if configured to do so):

  • Execute transition on the issue: if ticked, the mail handler executes a workflow transition on the issue (see below for more details)
  • Initialize Issue Fields: if ticked, the mail handler looks up a Field Context and applies its field rules to initialize issue fields.
  • Override Issue Lookup: if ticked, the mail handler looks up a Field Context  and applies its issue lookup field rules to find the issue that can be associated with the incoming email.
(tick)
Mail Handler EventAn issue event that is fired for each incoming emails that the mail handler processes.(error)
Acknowledge New Issuesif an email template is selected here, it will be used to generate auto-acknowledge emails when a new issue is created from email.(error)
Acknowledge New Commentsif 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 email.(error)
User Recipients

This attribute deteremines how the mail handler should treat users recognized for recipient email addresses.

Options are:

  • save as watchers in the issue
  • save them in the selected user picker field
  • treat them as email addresses and save the email addresses in the recipient fields (see below)
(error)
Sender FieldCustom field selected here will be used to store email addresses of the email senders(error)
Recipient FieldCustom field selected here will be used to store email addresses of the email senders(error)
Copy Recipient FieldCustom field selected here will be used to store email addresses of the email senders(error)
Email Address ExclusionEmail addresses (one per line) entered here are not saved in the sender or recipient fields. Supports regular expressions, to make sure your email address exclusion will not run into problems include (?i) at the beginning of the email address.(error)
Split RegexRegular expressions (one per line) entered here are used to split email body by a delimited. See more details below.(error)
Jira Mail Strategy

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

Note

Please be careful to avoid email loops when sending emails between Jira instances.



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.

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


External Email SendersSpecify 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 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.

...