--- title: "Event-based actions" canonical: "https://support.appfire.com/space/JMWE/461996144/Event-based%20actions" format: markdown --- > Macro (aura-html) ## List of events > ℹ️ 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: > ℹ️ > ℹ️ - You can pick the **Issue Transitioned ***Synthetic* event over *System *event(s) like **Issue Resolved** (or **Issue Closed **or **Issue Reopened**), as it allows you to fire an event on transitions beyond those supported by system* *events. > ℹ️ - *System *events like **Issue Assigned **(and others) come with certain limitations (listed in the table below) where the respective event is not fired as expected always. In such scenario(s), you can use the **Issue Field Value Changed ***Synthetic *event instead, to monitor the *Assignee *field (and/or others) and not miss any change made to the field. | **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:
- Issue view screen - Edit issue screen - Issue transition screen - Post-functions - Groovy console or REST API calls | > 📝 **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.
> ⚠️ **Note**: When monitoring the field **Epic Link** with an event-based action, the action will fail if you are using *Jira version 8.4.1 or earlier*. > ⚠️ > ⚠️ This is due to a Jira bug where the listener is not triggered by changes in the **Epic Link** field. See the [bug report](https://jira.atlassian.com/browse/JSWSERVER-12299) for more information. | | **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:
- Manually using the `Create` button on the top navigation bar or cloning - Using post-function - Using REST API call | N/A | | **Issue Updated** | Triggered whenever any issue field value is changed using the:
- Issue view screen - Edit issue option - Groovy console | The following changes made to an issue do not trigger the **Issue Updated** event:
- Changing the assignee using the `Assign to me` link below the **Assignee **field - Adding or removing issue links, watchers, or voters - Adding or changing issue fields on a transition screen - Changing a field value using JMWE post function on the current issue when post function is positioned before the *Update change history* post-function | | **Issue Assigned** | Triggered whenever an issue is assigned to a new user using the:
- `Assign` action button on the top - `Assign to me` link to the right of the screen | The following changes to the Assignee field do not trigger the **Issue Assigned** event:
- Manually by entering a name or selecting from the drop-down - On issue edit screen - During transition - Using JMWE post-function - Using Groovy script | | **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:
- Using the *Issue vie*w screen - As a result of **Comment issue post-function**, where the **Send “Issue commented“ notification** option is enabled while configuring the post-function** ** | The following changes to an issue do not trigger the **Issue Commented** event:
Adding a comment:
- While transitioning an issue - On the edit issue screen - Using the *Comment issue *post-function where **Send “Issue commented“ notification** option is disabled | | **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:
- In the Issue view - Using the Groovy console or REST API | 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:
- In the issue view - Using the Groovy console or REST API | 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:
- Manually - Using the Groovy console or REST API | 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](https://confluence.atlassian.com/adminjiraserver/adding-a-custom-event-938847495.html#Addingacustomevent-Customevents) to learn about adding custom events. | N/A |