fix:Triggered Alerts Notification #11719
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
aqibmohammadkhan
force-pushed
the
APIM-9149-Triggered-alerts-do-not-send-notification
branch
from
b23e186 to
2419ada
Compare
|
Raising a different one due to multiple commits |
jgiovaresco
deleted the
APIM-9149-Triggered-alerts-do-not-send-notification
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue
https://gravitee.atlassian.net/browse/APIM-9149
Description
Triggered alerts do not send email notification.
there was a type casting error when typecasting from v4planentity to rest.api planentity
Additional context
📚 View the storybook of this branch here