-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Track Sentry Issue Merges in Activity Tab #81352
Labels
Comments
Auto-routing to @getsentry/product-owners-issues for triage ⏲️ |
Thanks a lot for sharing this feedback, the team has added this to our backlog |
After my analysis on Slack, I found that this is not applicable. I will follow up in #proj-grouping on how to prevent this from happening. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem Statement
Sometimes Sentry will merge issues or at least mark issues as merged in the Merged Issues tab, without user interaction. In those cases, it can be hard to find out why the issues were merged and there's no entry in the activity tab about how the fingerprints ended up being merged.
Solution Brainstorm
If there is a heuristic for Sentry to auto-merge issues, make sure it is tracked in the activity tab to be able to track and understand what happened.
Product Area
Issues
The text was updated successfully, but these errors were encountered: