Please note this is related to Auditing and Search updates related to the 4.0.15 release. |
Status
A less verbose state which tells the user what point the incoming mail event processing is at. Allows users to search for inhibited events which is a state shared by many outcomes.
Name | Reason |
---|
| Pending follow up from a user to create a related user account. |
| JEMH should not process the message and was processing was stopped on purpose due to filters i.e. Catch Email Address filter, Blocklisting |
| JEMH should not process the message and was processing was stopped on purpose due to something other than filters. I.e inhibition through scripting |
| JEMH was prevented from processing further i.e. a Server Exception |
| JEMH processed the message ( all filters have passed ) |
| JEMH event was re-processed |
| JEMH is in processing the incoming mail. |
(Since 4.1.51 and 4.2.10) | There was an exception when processing an attachment and this has meant that the attachment was not added to the issue. More info about the exception can be found within the Report. |
| Either: |
| |
Outcome
A more verbose state which indicates to the user why a status was set i.e. the outcome was Folder Closed causing an inhibited state.
Name | Deletes the mail? | Can be scripted | Additional Behaviour | Causes |
---|
| | | | |
| | | | |
| | | | Can be triggered by Profile level Filter handling i.e. Precedence Bulk Filter. Can be triggered by Profile level Allowlist Handling Can be triggered manually through scripting
|
| | | | |
| | | Sends a Forward notification to the 'forward' address, and delete the message from the mailbox | Can be triggered by Profile level Filter handling i.e. Precedence Bulk Filter. Project Permission failure during processing i.e. User does not have commenting permission Can be triggered by Profile level Allowlist Handling Can be triggered manually through scripting When rejecting and HintOgram is not enabled then a forward will used instead Commit Limit handling Internal Error occuring during: Issue creation Issue update Profile Retrieval
|
| | | | |
| | | | Global Blocklisting match Can be triggered by Profile level Allowlist Handling Can be triggered by Profile level Filter handling i.e. Precedence Bulk Filter. Can be triggered manually through scripting
|
| | | | |
| | | Send a reject Hint Notification to the sender and delete the message from the mailbox. More info here: JEMH Hint Notifications | Can be triggered by Profile level Filter handling i.e. Precedence Bulk Filter. Can be triggered manually through scripting Thread match reject match Commit Limit handling Unable to find matching issue via directives/summary/subject User type permission i.e. if Non-Jira tries to create an issue via Jira user restricted profile If a valid Project Mapping is found: No Project match was during incoming mail processing (this is to stop admin mailboxes from being spammed). Comment Visibility permission failure Comment creation processing failure
From Address was not found incoming mail Worklog processing exception Nagios Field Map Extraction exception XML Field Map exctraction exception Reporter failed create/update/comment on an Issue
|
| | | | |
| | | | |
| | | | |
| | | | Either: |