java.lang.Object | |
↳ | com.atlassian.jira.event.issue.AbstractIssueEventListener |
Known Direct Subclasses |
Known Indirect Subclasses |
Subclasses of IssueEventListener can now override relevant functions in the interface as opposed to having to provide a dummy implementation for all methods.
Public Constructors | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Public Methods | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Implement this method to deal with any custom events within the system
| |||||||||||
Returns the parameters used by this listener.
| |||||||||||
Returns a textual description of the listener.
| |||||||||||
Indicates whether this listener is internal, meaning it cannot be
removed by an administrator.
| |||||||||||
Indicates whether JIRA should only create one instance of this listener.
| |||||||||||
Fired when an issue is assigned or unassigned.
| |||||||||||
Fired when an issue is closed.
| |||||||||||
The default behaviour for this method calls
issueUpdated(IssueEvent) . | |||||||||||
Fired when a user comments on an issue.
| |||||||||||
Fired when an issue is created.
| |||||||||||
Fired when an issue is deleted.
| |||||||||||
Fired for all other events, eg.
| |||||||||||
Fired when an issue is moved.
| |||||||||||
Fired when an issue is reopened.
| |||||||||||
Fired when an issue is resolved.
| |||||||||||
Fired when user starts work on an issue (start progress)
| |||||||||||
Fired when user stops work on an issue (stop progress)
| |||||||||||
Fired when an issue is updated.
| |||||||||||
Fired when work is logged against an issue.
| |||||||||||
Determines how the event should be processed.
|
Protected Methods | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
[Expand]
Inherited Methods | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
From class
java.lang.Object
| |||||||||||
From interface
com.atlassian.jira.event.JiraListener
| |||||||||||
From interface
com.atlassian.jira.event.issue.IssueEventListener
|
Implement this method to deal with any custom events within the system
event | IssueEvent |
---|
Returns the parameters used by this listener.
Returns a textual description of the listener. You can include HTML if required, but do not use tables or DHTML, as the description may be displayed inside tables or frames.
A good description will describe what this listener does and explain the parameters required for configuring it.Indicates whether this listener is internal, meaning it cannot be removed by an administrator.
true
if this is an Atlassian listener, otherwise Indicates whether JIRA should only create one instance of this listener. For example, having multiple mail listeners would be fine if you wanted multiple mails sent out. For other listeners, such as cache listeners, it makes no sense to have multiple instances.
Fired when an issue is assigned or unassigned.
Check the issue assignee to work out which is the case.Fired when an issue is closed.
The closure comment (if there is one) will be attached to the event as an action.The default behaviour for this method calls issueUpdated(IssueEvent)
.
This preserves the behaviour of JIRA prior to v5.2
Fired when a user comments on an issue.
The comment will be attached to the event as an action.Fired for all other events, eg. those fired from new workflow transitions.
Fired when an issue is resolved.
The resolution comment (if there is one) will be attached to the event as an action.Fired when user starts work on an issue (start progress)
Fired when an issue is updated.
The update changelog will be attached to the event as an action.Fired when work is logged against an issue.
The work log will be attached to the event as an action.Determines how the event should be processed. Based on the event type ID within the event, the appropriate actions are called.
An event with an unknown event type ID is logged and discarded. The customEvent method should be implemented to deal with any custom events that are added to the systemevent | - the IssueEvent object containing the event type ID |
---|