Versions Compared

Key

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

...

Setting

Details

Project Keys

Common to both Jira and Non-Jira notifications this field identifies what Project issue events should be handled within the current notification mapping.

The format of this can be a mix of one or more (comma separated)

  • Project keys (e.g. AAA) to allow per-project specific notification mappings

  • Regular Expressions (e.g. .* ), this allows one expression to match all or a subset of projects

Blocklist Project Keys

Defines Project Keys that should not use this Notification Mapping. Typically applies when using a Regular Expression to gather the Project Keys.

Notification Scheme

The notification scheme that should be followed for notifications to Jira users in this notification mapping

Exclude Subject Prefix

Allows you to remove the Subject Prefix (defined in - Outbound SMTP Mail Server) from outbound notifications

Require BROWSE_ISSUE

Allows notifications to only be sent to Jira users that have BROWSE_ISSUE project permission

Notify Me Condition

Defines how the event listener should decide if a user that triggered an event should be notified also

  • userPreference  -  only notifies initiating user if their user profile it set to do so

  • always  -  always notifies the initiating user of event

  • forSelectedEvents  -  notifies initiating user for events specified from Notify Me Events list

Notify Me Events

When forSelectedEvents is chosen for condition, selected events in list will result in notification for initiating user

Group Restriction

The user group that is used by Group Restriction Condition to specify who is notified.  See also: Event Listener Group Restriction and Conditions

Group Restriction Condition

How the specified group is used to specify who is notified.  See also: Event Listener Group Restriction and Conditions

Included Mail Headers 

SMTP headers containing issue properties can be added to notifications.  This allows the recipients of the mail to sort by these properties

Include Attachments in Notifications 

Attachments added in the last 10 seconds from event time can be chosen to be added to messages

Inline Images

Images referred through wiki mark-up in the content can be chosen to be displayed in-line

Attach Inlined Images

If enabled, the Inlined images will also be attached to email.

Store Notification History

If enabled, notifications sent by JEMH through the Event Listener will be tracked in the Notification History Issue Tab for issues in that project.  See Enable the Notification History Issue Tab for more information

Disable local links

This will disable any links that reference locations that start with the Jira base URL.

Event Selector and Filter script

Allows velocity script to be used to enable logic to be applied in order to change how a notification is handled.  Please see Change the EventID or Ignore an Event for more information

Treat Events with Comments As

When an issue event has a comment tied to it when it is fired, the event listener can be configured to notify of this event as if it were a different issue event (e.g. all events as ISSUE_COMMENTED)

Require a comment to notify 

Enabling this prevents issue events from resulting in notifications unless a comment is also contained within the event

Filter Mentioned Users

If a comment is present that the notification recipient is mentioned within then JEMH will filter this notification to prevent duplicate notifications.

Bcc Addressees

Email addresses added here are added to outbound notifications as Bcc

Custom From: Custom Field

Allows a custom field to provide the From address used in notifications

Custom From: Address

Allows a specified email address to be used as the From address in notifications

Use System Defined personal

Gathers the rendered Email from value that is defined in “System > General Configuration > Email From” and will use this as the Personal.

Custom From: Personal Custom Field

Allows a custom field to provide the Personal name of the From address in notifications

Custom From: Personal

Allows a specified name to be used as the Personal name of the From address in notifications

Custom Reply-To: Address Custom Field

Allows a custom field to provide the Reply-To address used in notifications

Custom Reply-To: Address

Allows a specified email address to be used as the Reply-To address in notifications

Custom Reply-To: Personal Custom Field

Allows a custom field to provide the Personal name of the Reply-To address in notifications

Custom Reply-To: Personal

Allows a specified name to be used as the Reply-To Personal name in notifications

Use Request Participants

Notifies the Request Participants in addition to recipients in the Notification Scheme. No duplicate notifications will occur.

Note: This will only send Comment notifications.

Notify participants of events without comments

This will also notify Request Participants of events that do not contain a comment.

Use Organizations

Notifies members of Organizations who have been involved on the issue and has enabled notifications within the Customer Portal for that particular issue, in addition to recipients in the Notification Scheme. No duplicate notifications will occur.

Use Customer Notification Templates

Allows separate Notification Template selection for customer users. If enabled and no template is selected for an event, the customer will not be notified.

...

Filter by label (Content by label)
page
showLabelsfalse
max5
spacesJEMH
showSpacefalse
sortmodified
showSpacetypefalsepage
reversetruetype
labelsevent listener jemh issue notification
cqllabel in ( "listener" , "event" , "issue" , "notification" , "notifcations" ) and type = "page" and space = "JEMH"labelsevent listener jemh issue notification
Page Properties
hiddentrue


Related issues



...