"The oldest adopted release associated with the event's issue is newer than the latest adopted release in <environment>" should not consider "oldest adopted release"

[JParisFerrer]

Problem

When using the "The oldest adopted release associated with the event's issue is newer than the latest adopted release in " filter in an issue alert, the alert will report old, non-new issues as new issues due to the "incorrect"/not useful use of Adopted releases only.

NOTE: This is different from the "latest adopted release in ". In this scenario, relying on adoption makes sense.

Expected Behavior

In this example, we have two environments, "beta" and "alpha" and are using semver releases. Alpha releases are released daily and eventually promoted in a weekly beta release. Assume Beta is at v210 and Alpha is at v211

1. I setup an alert with "The oldest adopted release associated with the event's issue is newer than the latest adopted release in beta" filter
2. An issue that has a "First Seen" time (as seen on the issues page) of v206 in beta (and prod) that is first seen in an adopted alpha release should not trigger the alert

Actual Behavior

1. I setup an alert with "The oldest adopted release associated with the event's issue is newer than the latest adopted release in beta" filter
2. An issue that has a "First Seen" time (as seen on the issues page) of v206 in beta (and prod) that is first seen in an adopted alpha release triggers the alert

We suspect that this is because we recently added release health, so the v206 release the issue was first seen in was not considered Adopted. However, this doesn't make sense -- whether a release was adopted or not, if that issue was present in that release it will not be a regression in a future release as the code in that unadopted release had the issue already present. However, even without this wrinkle of recently introducing sessions to the application, we believe this issue can occur for any issues which are environment dependent. For example, a feature that is heavily used in beta or prod but very rarely used in alpha, meaning that whenever it is used in alpha and triggers an exception, it could trigger the alert if the alert is filtered to the alpha environment

PS: this is associated with a customer case which has more links associated

[getsantry]

Assigning to @getsentry/support for routing ⏲️

[getsantry]

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

[rachrwang]

Thank you for filing this @JParisFerrer - we'll work with the client team to prioritize and communicate next steps on this issue

[armenzg]

Tomorrow I will be deploying #80737 and may fix the issue.
Your organization has opted in for the fix.