Creating an alert using `release.stage: adopted` in the Sentry web UI throws a 500 error

[arifken]

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

1. Navigate to Alerts > Create Alert > Crash free user rate
2. Select a project and environment
3. for filters, enter release.stage:adopted
4. Set some thresholds below (I used 99.5 as critical, 99.7 as warning and 99.75 as recovery)
5. Name the alert
6. Click "Add alert"

Expected Result

The alert should be created and visible in the Alert list.

Actual Result

An error appears in lower right of the screen:

And in the console the message

Failed to load resource: the server responded with a status of 400 ()
us.sentry.io/api/0/organizations/REDACTED/alert-rules/?duplicateRule=false&referrer=alert_stream&sessionId=REDACTED&wizardV3=true:1 

Failed to load resource: the server responded with a status of 500 ()

Product Area

Alerts

Link

No response

DSN

No response

Version

No response

[getsantry[bot]]

Assigning to @getsentry/support for routing ⏲️

[getsantry[bot]]

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

[ceorourke]

@iambriccardo I reproduced this and tracked the error id to this Sentry issue that's assigned to your team, can you take a look? I don't see a telemetry team on GitHub to assign this to.

[rachrwang]

@iambriccardo - do you have any updates to share on this ticket? Thanks!

[iambriccardo]

Hi, sorry, I completely missed the notification. I will check it out!

[matejminar]

There seems to be a bug in UI that let's you add all kinds of filters to session alerts. Session alerts support only a very small subset of filter conditions and I believe release.stage is not one of them. We'll get this fixed 🙏