HOLD

Pending follow up from a user to create a related user account.

INHIBITED

JEMH should not process the message and was processing was stopped on purpose i.e. Outcome = FORWARDED, REJECTED, DROPPED, BLOCKED

PROCESSED

JEMH processed the message ( all filters have passed )

RE_PROCESSED

JEMH event was re-processed

RUNNING

JEMH is in processing the incoming mail.

UNKNOWN

Either:

• the incoming mail process has just begun

• An unknown status occurred i.e. null status (this is a bug)

BLOCKED

• JEMH cannot process the mail i.e. there is a blocking condition(s):

  • JEMH is diasbled

  • Incoming Mail Message is null during processing ( i.e retrieval problem)

  • Jira Storage Issues:

    • Low disk space: Jira has less than 250MB available to store audit events

    • Jira Process User lacks write permission: <JIRA HOME>/jemh/data is not writable by the process user

DELETED

• Notification Summary Filter match

DROPPED

• 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

FOLDER_CLOSED

• An IMAP folder closed during mail retrieval. Please see: https://thepluginpeople.atlassian.net/wiki/spaces/KB/pages/3397222401/Why+do+FolderClosedException+occur#JEMH

FORWARDED

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

HOLD

• Requires further reprocessing to re-process the content once a user account has been added

IGNORED

• 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

INTERNAL_ERROR

• An Exception during processing

• No issue(s) was updated/created/commented

REJECTED

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

REMOVED

• JEMH Audit file could not be created as the message was removed from the mail server before it could be read fully (javax.mail.javax.mail.MessageRemovedException)

RUNNING

• Event is still being processed

SUCCESS

• Derived from CAN_HANDLE no issues detected during processing

UNKNOWN

Either:

• The incoming mail process has just begun

• An unknown outcome occurred i.e. null outcome (this is a bug)