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

Multiple Issue Alerts in a single Slack Alert Thread #70135

Closed
kpujjigit opened this issue May 2, 2024 · 4 comments · Fixed by #70108
Closed

Multiple Issue Alerts in a single Slack Alert Thread #70135

kpujjigit opened this issue May 2, 2024 · 4 comments · Fixed by #70108

Comments

@kpujjigit
Copy link

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

Set up Slack Integration
Construct Issue Alert with routing to a Slack Channel
Trigger an Issue Alert multiple times to send multiple alerts per a single issue

Expected Result

New events that are grouped with an existing issue are being posted into a slack thread rather than to the main slack channel, resulting in poor visibility for recurring issues.

Actual Result

It appears the logic of this change (Slack Threads for Metric Alerts) is applying to Issue Alerts unintentionally.

Product Area

Settings - Integrations

Link

No response

DSN

No response

Version

No response

@getsantry
Copy link
Contributor

getsantry bot commented May 2, 2024

Assigning to @getsentry/support for routing ⏲️

@Dhrumil-Sentry
Copy link

Thanks for this report - This was a feature released to Early Access customers only for feedback and we will update this so that the issue alerts always go to the channel

@getsantry
Copy link
Contributor

getsantry bot commented May 2, 2024

Routing to @getsentry/product-owners-settings-integrations for triage ⏲️

@ykamo001
Copy link
Member

ykamo001 commented May 2, 2024

Fix is released, please let us know if there's any other issues or it continues to be there!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants