feat(issues): Remove fake auto-resolution#120153
Open
scttcper wants to merge 2 commits into
Open
Conversation
Auto-resolution is persisted by the background task now, but model and serializer paths still inferred resolved state from last_seen. Remove that legacy status override along with the search and regression workarounds it required. Co-Authored-By: Codex <noreply@openai.com>
Remove tests that only assert the deleted inference stays deleted, plus inert resolve_age setup copied into event lookup tests. Co-Authored-By: Codex <noreply@openai.com>
cvxluo
approved these changes
Jul 20, 2026
wedamija
approved these changes
Jul 20, 2026
wedamija
left a comment
Member
There was a problem hiding this comment.
Lol, I can't believe this was replicated in so many places. Nice clean up
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Remove the fake read-time auto-resolution status and the workarounds it required. Issues pending auto-resolution now stay unresolved until the background task persists the transition. The auto-resolution task is being adjusted from 1 hour intervals to 10 minutes in #120149
some history:
last_seenand the project's resolve age, returningresolvedwhile the database row was still unresolved.statusDetails.autoResolvedwas added in 2015 for #2341 so the UI could explain why unresolve did not stick and disable that action.Refs https://linear.app/getsentry/issue/ID-1710