Summary
This section allows you to specify the Issue defaults that can be applied when not already provided and also allows to configure the Loop detection parameters.
Configuration Options
Use Mail XHeader Priority
When enabled the emails header X-Priority will be scaled by value (1-5) to the range of available Jira priorities. For more information see: Using X-Priority Headers
Summary
This is a default Issue Summary that is used when an incoming email does not contain a Subject.
Comment
A default comment that is used when a commenting email does not contain a email body.
IssueLink type
Default Issue Link Type. This is used when there is no Link Type specified. Current options are:
Blocks
Cloners
Duplicate
Problem/Incident
Relates
Worklog Security Role
A default security Role that will be applied to worklog notes if this is not specified.
Worklog Security Group
A default security Group that will be applied to worklog notes if this is not specified.
Add Sender As Watcher
Automatically adds the sender as a watcher to created issues, (not necessarily with right-to-use). Sender must have a Jira account.
3rd Party CF Support
If enabled, JEMH will attempt to initialise 3rd party Custom Fields with String (text) values supplied. Problems with such initialisation will be logged at INFO level only.
Add Issue Entity Properties
This feature helps mail clients thread Jira notifications into the conversation that drove their creation. It enables JEMH to store the incoming message Message-ID, References and In-Reply-To headers during issue creation. For more information see: Associate issue creation and other events with initial email Thread
Entity Properties can only be set after the issue is created, so the CustomOnCreate event is needed for create notifications to be tagged with the Email’s Message-Id. NOTE: Setting Entity Properties is considered by Jira to require EDIT_ISSUE permission, so is not enabled by default.
Default Due Date (days)
Sets the default due date of issues created by email, at a point “n” working days in the future.
Date Formats
Comma separated list of Java Date formats to be accepted. e.g. for dueDate processing or Date Custom Fields. e.g. yyyy/MM/dd.
For more help see: https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html
Date Time Formats
Comma separated list of Java Date and Time formats to be accepted. e.g. for dueDate processing or Date Custom Fields. e.g. dd/MMM/yyyy h:mm.
For more help see: https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html
Issue Comment Limit
This is the maximum number of comments that is allowed on a issue before the limit is exceeded. Addresses looping problems. Default value is 50, set to 0 for unlimited.
Issue description/comment max characters
The maximum character limit for descriptions and comments. Set to 0 for unlimited number of characters. Cannot be greater than the Jira System value set within Jira Administration > System > General Configuration > Advanced Settings > jira.text.field.character.limit.
Limit exceeded action
This is the action that will be performed if the comment limits are exceeded. Current options are:
Forward to the Forward User (Specified in Notification section)
Reject
Truncate