Versions Compared

Key

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

...

The above configuration will result in a message rejection when an incoming email attempts to comment on an in issue that is in the defined status. The sender of the email will be notified of the message rejection via an email that will be generated using the project mapping defined message rejection template set. The end user will receive a rejection email similar to the following:

...

Configure message rejection when issue matches JQL query

As an Admin, you may want to disable JEMHC from commenting on issues matching a specified JQL status, rather than matching against Issue Statuses. This feature can be configured to reject issues matching the JQL query defined via the “Reject comment on JQL Match” field.

...

When the defined JQL query matches a given Issue, the attempt to comment on the existing issue is rejected.

Configure message rejection for issues that have been in resolved status for X days:

As an administrator you may want to prevent users from commenting on issues that have been in a resolved status for a specific period of time, this can be useful to encourage users to create new issues once a previous issue has been resolved for a while. The "Reject Comments When Issue Resolved For More Than Days" field allows you to define a number of days that an issue in resolved status can be commented on before an issue becomes locked for commenting. After the number of days has elapsed any comment on the issue will be rejected and a rejection notification will be sent to the sender of the comment email.

Configuration to disable comments on issues that have been in resolved status for more than 1 day:

...

Rejection notification received by the sender of the rejected comment email:

...

...

Configure new issue creation during message rejection match

Some customers may want to process the message regardless, by creating a new issue, rather than resulting in message rejection for the issue comment. This can be configured by enabling the “Issue creation on Comment Rejection Match” setting.

This setting is only visible if you have configured one of “Reject comment on Status”, “Reject Comments When Issue Resolved For More Than Days” or “Reject comment on JQL Match” message rejection features.

...

When enabled, any issue comments that would be rejected (Either via status match or JQL match) will create a new issue, using the attempted comment as the new issue’s description.

Configure message rejection notification when issue comment limit has been reached:

...

The above configuration will results in a rejection message being sent to the email sender when a comment on an issue has been rejected due to the issue comment limit being reached:

...

Configure message rejection for issues that have been in resolved status for X days:

As an administrator you may want to prevent users from commenting on issues that have been in a resolved status for a specific period of time, this can be useful to encourage users to create new issues once a previous issue has been resolved for a while. The "Reject Comments When Issue Resolved For More Than Days" field allows you to define a number of days that an issue in resolved status can be commented on before an issue becomes locked for commenting. After the number of days has elapsed any comment on the issue will be rejected and a rejection notification will be sent to the sender of the comment email.

Configuration to disable comments on issues that have been in resolved status for more than 1 day:

...

Rejection notification received by the sender of the rejected comment email:

...

Configure message rejection notification when processing mode is comment only:

...

Rejection notification received by the sender of the rejected email:

...

Message rejection based on JQL match

Similar to JEMH Server/DC, the ability to reject a message based on the JQL match allows expanded rejection criteria, as opposed to simply rejecting based on Issue Status.

Info

This feature is currently in Development - Please see

Jira Legacy
serverSystem JIRA
serverId31e1f342-5dce-3979-a43c-85899d565476
keyJEMHC-2678
for internal updates

New Issue creation during Message rejection match

Similar to JEMH Server/DC, this setting provides the ability to select whether messages are rejected (notifying using the rejection template), or if new Issues can be created if there is a message rejection match.

...

Jira Legacy
serverSystem JIRA
serverId31e1f342-5dce-3979-a43c-85899d565476
keyJEMHC-2679

...

Filter by label (Content by label)
showLabelsfalse
max5
sortmodified
showSpacefalse
reversetrue
cqllabel in ( "notifcations" , "template" ) and space = "JEMHC" and type = "page"