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.