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.

Sign up for GitHub

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

Jump to bottom

Direct paging for acknowledged alert group is confusing #4761

Closed
vstpme opened this issue Jul 30, 2024 · 2 comments
Closed

Direct paging for acknowledged alert group is confusing #4761

vstpme opened this issue Jul 30, 2024 · 2 comments
Assignees
@vstpme
Labels
bug Something isn't working part:alert flow & configuration

Comments

@vstpme
Copy link
Member

vstpme commented Jul 30, 2024

What went wrong?

What happened:

  1. I added a responder for an existing acknowledged alert group
  2. The user received a notification but unable to stop their personal notifications because alert group is already acknowledged

What did you expect to happen:

  1. I add a responder
  2. They receive a notification and are able to stop their personal notifications (without resolving the alert group)

How do we reproduce it?

–

Grafana OnCall Version

v1.8.8

Product Area

Alert Flow & Configuration

Grafana OnCall Platform?

Docker

User's Browser?

No response

Anything else to add?

No response
@vstpme vstpme added the bug Something isn't working label Jul 30, 2024
@vstpme
Copy link
Member Author

vstpme commented Jul 30, 2024

Similar issue with acknowledging direct paging alert groups: #4760

@vstpme vstpme self-assigned this Aug 29, 2024
@vstpme vstpme mentioned this issue Aug 29, 2024
Merged
3 tasks
@vstpme
Copy link
Member Author

vstpme commented Aug 30, 2024 •
edited
Loading

with #4957 merged it's now possible to at least unacknowledge and then re-acknowledge an alert group back to stop notifications

github-merge-queue bot pushed a commit that referenced this issue Aug 30, 2024
@vstpme
Fix direct paging ack (#4957)
7b74b65 
# What this PR does

Fixes #4760 (also provides a
workaround for #4761)

## Checklist

- [x] Unit, integration, and e2e (if applicable) tests updated
- [x] Documentation added (or `pr:no public docs` PR label added if not
required)
- [x] Added the relevant release notes label (see labels prefixed w/
`release:`). These labels dictate how your PR will
    show up in the autogenerated release notes.
@vstpme vstpme closed this as not planned Won't fix, can't repro, duplicate, stale Aug 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@vstpme vstpme

Labels
bug Something isn't working part:alert flow & configuration
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@vstpme