-
Type:
New Feature
-
Status: Done (View Workflow)
-
Priority:
High
-
Resolution: Done
-
Affects Version/s: 4.3.0
-
Component/s: None
-
Labels:None
-
Sprint:Sprint 41, Sprint 42, Sprint 43, Sprint 44, Sprint 45, Sprint 46, Sprint 47, Sprint 48, Sprint 49, Sprint 50, Sprint 54
-
Critical Points:0.8
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
-
- Done
-
-
SRCONF-159 Support Comalatech events
-
- Done
-
- is related to
-
SRPLAT-437 Confluence Event listeners should be able to listen to events provided by plugins
-
- Done
-