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

Sentry automatically resolves user feedback after manually un-resolving #81894

Open
DAcodedBEAT opened this issue Dec 9, 2024 · 5 comments
Open

Comments

@DAcodedBEAT
Copy link

DAcodedBEAT commented Dec 9, 2024

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

  1. I have Linear attached to my Sentry account.
  2. A user provides feedback related to an existing issue, which I link to the corresponding ticket in Linear.
  3. The issue is auto-closed due to inactivity (as expected).
  4. I manually un-resolve the issue to keep it open.
  5. Sentry immediately resolves the issue again, despite my action to un-resolve it.

Expected Result

When I manually un-resolve an issue that was auto-resolved, Sentry should keep the issue in an unresolved state until I explicitly resolve it or until the auto-close duration has been met again.

Actual Result

Sentry automatically resolves the issue right after I manually un-resolve it.
Image

note: The update toast appears on every state change of this button, and the network tab in dev tools is showing 2xx HTTP responses when this happens.

Product Area

User Feedback

Link

No response

DSN

No response

Version

No response

@getsantry
Copy link
Contributor

getsantry bot commented Dec 9, 2024

Auto-routing to @getsentry/product-owners-issues for triage ⏲️

@getsantry getsantry bot moved this to Waiting for: Product Owner in GitHub Issues with 👀 3 Dec 9, 2024
@MichaelSun48
Copy link
Member

Hey @DAcodedBEAT, thanks for finding and reporting this bug!

We've been having some issues with issue status updates (like changing the resolution status) being slow to propagate, leading to UI jank like this. Can you confirm if that issue was correctly marked as unresolved eventually, or if it never fixed itself? Just narrow down if this might be related to that previous issue or if this is a new bug altogether.

@DAcodedBEAT
Copy link
Author

Hey @DAcodedBEAT, thanks for finding and reporting this bug!

We've been having some issues with issue status updates (like changing the resolution status) being slow to propagate, leading to UI jank like this. Can you confirm if that issue was correctly marked as unresolved eventually, or if it never fixed itself? Just narrow down if this might be related to that previous issue or if this is a new bug altogether.

Hey @MichaelSun48! Unfortunately, the issue didn't fix itself. :(

@getsantry getsantry bot moved this to Waiting for: Product Owner in GitHub Issues with 👀 3 Dec 11, 2024
@MichaelSun48
Copy link
Member

Gotcha, sorry to hear that! Let me track down someone that has domain expertise here and we'll try to get this prioritized. Feel free to follow up here for updates!

@JoshFerge
Copy link
Member

tracking down the logic where this happens,

happened = Group.objects.filter(

we do not take into account manual unresolves in our auto resolver right now. seems like that would be the root fix here.

@JoshFerge JoshFerge removed their assignment Dec 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

No branches or pull requests

3 participants