Unresolved/Archive issue status not filtering events on Explore -> Errors page.

[rodolfoBee]

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

1. Go to Explore -> Errors
2. Use the is:unresolved query

Expected Result

Only events from unresolved issues are returned.

Actual Result

The filter has no effect on the page. See screenshots:

Issues in the project: this project has one archived, one resolved, and one unresolved issue.

Searching for is:unresolved returns all issues (same behaviour for is not: resolved

Additionally, is:archived returns no issues:

And is:resolved returns the correct result:

Using is:ongoing is not an option:

Invalid value for "is" search, valid values are ['archived', 'ignored', 'muted', 'reprocessing', 'resolved', 'unresolved']

This search also affects the filters used in alerts, causing alerts to trigger/not trigger incorrectly.

Related to #122790

Reported in an internal ticket via support

Product Area

Explore

Link

https://dev-curumas.sentry.io/explore/errors/?dataset=errors&field=issue&field=count%28%29&field=count_unique%28user%29&name=All%20Errors&project=5591101&query=is%3Aunresolved&queryDataset=error-events&sort=-count%28%29&statsPeriod=24h&yAxis=count%28%29

DSN

No response

Version

No response

[getsantry]

Assigning to @getsentry/support for routing ⏲️

[linear-code]

ENG-8631

[getsantry]

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

[JoshuaKGoldberg]

We took a look - this seems to be due to stale rows in the group_attributes table that the errors dataset joins against. There's also already IS-17 around, so it looks like this is tracked by that. Transferring over to issues. Thanks for filing, this was an interesting one!