...
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
...
This is a default Issue Summary that is used when an incoming email does not contain a Subject.
Comment
A default comment/description that is used when a commenting email does not contain a email body.
...
Automatically adds the sender as a watcher to created issues, (not necessarily with right-to-use.Creation). Sender must have a Jira account.
...
| Info |
|---|
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. |
...
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
...
Related Pages
| Filter by label (Content by label) | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|