Issue reopened - An issue has been re-opened. Issue comment edited - An issue's comment has been modified. Issue commented - An issue has had a comment added to it. (Note that an issue may be closed without being resolved see statuses). Issue resolved - An issue has been resolved (usually after being worked on and fixed). Issue assigned - An issue has been assigned to a new user.
Issue updated - An issue has had its details changed. Issue created - An issue has been entered into the system. A custom event will only be fired if it is associated with a transition post function for an active workflow (see Managing your workflows). Note that the event state does not indicate whether the event is able to be fired. Inactive - the event is not associated with any notification schemes or workflow transition post functions.
Note that only inactive custom events can be deleted.Īn event can be in either of the following states:Īctive - the event is associated with at least one notification scheme or workflow transition post function. You can add and delete as many custom events as you need. You can, however, make them Inactive (see below).Ĭustom - Custom events are used to generate an email notification (or invoke a listener) from a particular workflow transition's post function.
System - System events are used throughout Jira internally, and cannot be added or deleted. There are two types of events within Jira: an Issue Resolved event, or a custom event (see below). Other events are fired from within workflow transition post functions - e.g. Some events are fired by Jira internally - e.g. the Issue Created event is fired when an issue has been created. Every issue operation within Jira is associated with a particular event - e.g. send an email notification) based on the event that has occurred. Jira uses an event-listener mechanism to alert the system that something has happened, and to perform appropriate action (e.g.
0 kommentar(er)
