Snigdha Sharma

Thanks, added to the team's backlog. I believe this is in the same space as some work we've been thinking about for upcoming quarters

Hm `ADD CONSTRAINT EXCLUDE` is an unsafe operation -- we can wipe the table and pause writes before applying this if that would make it safe? Otherwise the safer suggestion...

Talked to @wedamija - we'll turn off the ff for writes and run the post-deploy migration to delete rows before running this migration with SafeRunSQL.

@szokeasaurusrex [this test](https://github.com/getsentry/sentry/blob/6b87ddf79ef6388fc678bb395626921b7da9cc07/tests/sentry/api/endpoints/test_organization_releases.py#L1964-L1992) looks like it might mimic similar behavior of setting a specific scope and using the API token to test behavior

Turned off the feature that was responsible for this bug - searching for `is:unassigned` works now. Thanks for filing the issue @rodolfoBee