Skip to content
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

Allow customisation of the Slack UX #4165

Open
tyrken opened this issue Apr 5, 2024 · 1 comment · May be fixed by #4206
Open

Allow customisation of the Slack UX #4165

tyrken opened this issue Apr 5, 2024 · 1 comment · May be fixed by #4206

Comments

@tyrken
Copy link

tyrken commented Apr 5, 2024

What would you like to see!

I'm evaluating OnCall for alert notifications at our small company, but am a little concerned that the actual UX of the product, particularly on Slack doesn't match our ideal or will be particularly well received by my fellow coworkers.

E.g. the current Slack alert message includes a bunch of buttons we won't want, and a "Resolved by alert source/username" addon that seems unnecessary, at least in the main message rather than the log or thread. This take up valuable space which if you get multiple alerts at once can cause issues to be missed. I'm also concerned about over-notification e.g. #187 and #3849.

The latter issue is particularly worrying as a PR to allow customisation was offered in #3977 but rejected by the maintainers - but real users like us will have different requirements & expectations of what is "best" and unless you allow flexibility then we'll remain annoyed rather than being active promoters of your OSS project.

Product Area

Chatops

Anything else to add?

No response

@tyrken tyrken added the feature request New feature or request label Apr 5, 2024
Copy link
Contributor

github-actions bot commented Apr 5, 2024

The current version of Grafana OnCall, at the time this issue was opened, is v1.3.117. If your issue pertains to an older version of Grafana OnCall, please be sure to list it in the PR description. Thank you 😄!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants