List of events
Info |
---|
Synthetic events are specific to JMWE and are meant to capture changes irrespective of how they were made. These events offer more flexibility over the built-in Jira System events. For example:
|
Event type | Event | Description | Limitations | |
---|---|---|---|---|
Synthetic (JMWE specific events) | Issue Transitioned | Triggered when an issue is transitioned from the mentioned From Status(es) to the To Status(es). | N/A | |
Issue Field Value Changed | Triggered whenever the specified issue field(s) mentioned in Fields to monitor are updated. Issue fields can be modified using:
| Note: Not every field value change can be captured by JMWE (or other apps); if a change does not send an update event, it will not trigger an event-based action. It is highly recommended that you test your event-based actions thoroughly before deploying them to a production environment.
| ||
Issue Watcher Added | Triggered when a user starts watching an issue. | N/A | ||
Issue Watcher Deleted | Triggered when a user stops watching an issue. | N/A | ||
Issue Link Created | Triggered when a link is added to an issue. | N/A | ||
Issue Link Deleted | Triggered when a link is removed from an issue. | N/A | ||
System (Built-in Jira events) | Issue Created | Triggered whenever an issue is created:
| N/A | |
Issue Updated | Triggered whenever any issue field value is changed using the:
| The following changes made to an issue do not trigger the Issue Updated event:
| ||
Issue Assigned | Triggered whenever an issue is assigned to a new user using the:
| The following changes to the Assignee field do not trigger the Issue Assigned event:
| ||
Issue Resolved | Triggered when Jira fires the Issue Resolved event configured by the Jira administrator in the workflow post-function. | N/A | ||
Issue Closed | Triggered when Jira fires the Issue Closed event configured by the Jira administrator in the workflow post-function. | N/A | ||
Issue Commented | Triggered whenever a comment is added to an issue:
| The following changes to an issue do not trigger the Issue Commented event: Adding a comment:
| ||
Issue Comment Edited | Triggered whenever a comment on an issue is edited. | N/A | ||
Issue Comment Deleted | Triggered whenever a comment on an issue is deleted. | N/A | ||
Issue Reopened | Triggered when Jira fires the Issue Reopened event configured by the Jira administrator in the workflow post-function. | N/A | ||
Issue Deleted | Triggered whenever an issue is deleted. | N/A | ||
Issue Moved | Triggered whenever an issue is moved. | N/A | ||
Work Logged On Issue | Triggered whenever the worklog (typically in hours) is added to the issue:
| N/A | ||
Work Started On Issue | Triggered when a Jira administrator configures a Jira workflow to fire an event whenever an assignee starts working on an issue | N/A | ||
Work Stopped On Issue | Triggered when a Jira administrator configures a Jira workflow to fire an event whenever an assignee stops working on an issue | N/A | ||
Issue Worklog Updated | Triggered when a Jira administrator configures a Jira workflow to fire an event whenever the worklog of an issue is modified:
| N/A | ||
Issue Worklog Deleted | Triggered when a Jira administrator configures a Jira workflow to fire an event whenever the worklog of an issue is deleted:
| N/A | ||
Generic Event | Triggered whenever a generic event is invoked by a worklog post-function. A generic event can be configured to invoke a listener (or can be customized). This event is triggered by default while running a post function during a transition. In a scenario where the administrator does not configure a Generic event by default, this event is not triggered. | N/A | ||
Custom (Customized events that invoke a listener) | Events (both active and inactive) configured on your Jira instance are displayed here | Triggered whenever the respective custom event is fired by Jira. Click here to learn about adding custom events. | N/A |