Eg tempo events: https://answers.atlassian.com/questions/38738244/how-to-email-tempo-timesheet-on-approval
Probably they would need to type the FQCN, as the tempo events don't have a common base class.
Same applies to com.atlassian.jira.plugins.share.event.ShareIssueEvent.
AbstractFieldConfigSchemeEvent which is triggered when the field configuration changes (options added / removed in a select list)
Derived from trigger on CustomfieldUpdatedEvent
Also true for Bitbucket events that come from Bitbucket plugins like RefRestrictionUpdatedEvent, RefRestrictionAddedEvent, and RefRestrictionDeletedEvent, which control branch permissions.
- is duplicated by
SRJIRA-2374 Add Listener Compatibility for JIRA Agile events
SRCONF-159 Support Comalatech events
- is related to
SRPLAT-437 Confluence Event listeners should be able to listen to events provided by plugins