Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Summary

When there has been a change on a issue this will result in Jira sending an event to JEMHC so that it can be processed and send the relevant notifications. This page displays all of the events that have been sent to JEMHC for processing.

Event Report

For each event there is a Report which will display additional information about the processing of the event. This includes who was notified and if there was any issues during the processing of the event.

This will display a report similar to the following. The report will show any relevant information about the event and if there was any issues.

Event Statuses

For each audit report there is a status which defines the outcome of processing that event. Below are the status that are currently used within the Events auditing page.

Status

Description

Queuing

The Event is currently queued as it is waiting for the next minute interval. This so that other events created within the interval can be merged into one notification.

Processing

The Event data is currently being processed by JEMHC.

Success

The event was processed correctly and resulted in a notification being sent to a recipient.

Ignored

Audit event did not send a notification as there was either no recipients or the template did not render any content within the notification.

Typically caused by not using $jemhUtils.setFieldRendered() within the macro/template. See the Macro documentation for more info about $jemhUtils.setFieldRendered(): Velocity Macro Scripting and Notifications

Events failed to process

When webhook events fail to be processed, they are retried. Once all retry attempts have been used, the event goes into ERROR state. These messages are displayed in the ‘Failed Events’ auditing tab.

  • No labels