@ParametersAreNonnullByDefault @ReturnValuesAreNonnullByDefault
EmailTemplatesDownloadedEvent)
Email templates uploaded (EmailTemplatesUploadedEvent)
Email templates validated (EmailTemplatesValidatedEvent)
Email templates applied (EmailTemplatesAppliedEvent)
Email templates reverted (EmailTemplatesRevertedEvent)
See: Description
| Class | Description |
|---|---|
| BaseEmailTemplatesEvent | |
| EmailTemplatesAppliedEvent | |
| EmailTemplatesDownloadedEvent | |
| EmailTemplatesRevertedEvent | |
| EmailTemplatesUploadedEvent | |
| EmailTemplatesValidatedEvent |
| Enum | Description |
|---|---|
| EmailTemplatesValidatedEvent.ValidationFailureReason |
EmailTemplatesDownloadedEvent)EmailTemplatesUploadedEvent)EmailTemplatesValidatedEvent)EmailTemplatesAppliedEvent)EmailTemplatesRevertedEvent)Each of the events has three parameter:
sessionId, which should be used to correlate events in a single flow (for analytics)operationSuccessful, containing information whether operation ended successfullyuser, which is ApplicationUser performing operation. This is not used by analyticsEmailTemplatesValidatedEvent has validationFailureReason,
which contains the reason (com.atlassian.jira.event.mail.template.EmailTemplatesValidatedEvent.ValidationFailureReason)
of validation failure if operation wasn't successful. Otherwise, it's null.
Unless otherwise noted, all parameters are supposed to be used by analytics
Copyright © 2002-2024 Atlassian. All Rights Reserved.