-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Being able to edit the notification that is being sent out #3048
Comments
I would like this too, with another (optional) textbox under 'Description' for 'Notification Message' that could include info on how to deal with the problem or a link to a Playbook. |
ooooo, it would be nice to be able to automate actions if something goes south |
Yes duplicate of #646 - I would say close this issue |
@4n0nh4x0r could you close this issue? |
@4n0nh4x0r |
🏷️ Feature Request Type
New Notification, UI Feature
🔖 Feature description
As the title already says.
It would be nice to be able to specify what a notification sends.
Like for example, if i dont want to expose the ip address of the server where my backend service runs on, it would be nice to be able to at least disabled that the notification sends out the service url.
Even better would be being able to fully customize the notification but well, i can assume how much work that would be, so it would already be nice to just be able to toggle the visibility of certain parts of the message.
✔️ Solution
Having options in the notification setup that you can toggle to enable/disable this specific notification from showing a certain part of the information like for example the service url or the ping.
At least a toggle to disable the service url from being shown on the notification you are editing.
❓ Alternatives
Alternatively one could allow the user to create their own notification with maybe a specific json object template they have to edit themselves, or just some text boxes that fill the json object behind the scenes
📝 Additional Context
No response
The text was updated successfully, but these errors were encountered: