Resolved issues don't appear to check the release before regressing

[dazzknowles]

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

We had a an issue come in on a production environment which is running version 3.25.47.21 and I marked the issue as resolved in the next release. I then deployed the next release (3.25.47.22) to the customer's UAT environment for their sign-off.

A little later the error occurred again on production and so it regressed the fix but it's still running the older version so it's not a regression.

Expected Result

The error should instead have just been recorded as another event on the existing resolved issue and the status left unchanged.

Actual Result

Product Area

Issues

Link

No response

DSN

No response

Version

No response

[linear[bot]]

ENG-6071

[getsantry[bot]]

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

[scttcper]

Can you post a link to the issue, the activity includes a event id in the json of the event that caused the regression. This may not be the recommended or latest event.

[dazzknowles]

Thanks @scttcper, have sussed it out. Your comment made me double check and indeed I had the issues filtered to production which also limits the events shown against the issue to only those in the filtered environment so the cause of the regression did happen on the new version, but wasn't shown in the list of events.

Maybe that view could highlight that there are other instances from other environments, and/or the regressed note in the activity include a link to the event that triggered it?

[yuvmen]

Thanks @dazzknowles! , we will consider adding some indication there as you suggested, I have added it to our backlog 👍