getsentry / getsentry/sentry

Release filtering does not work as expected in Discover

Open
#37,871 2 comments 0 reactions 1 assignee Claimed by @shruthilayaj View on GitHub
Bug Feature Product Area: Discover
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
1d 5h
Merged PRs (30d)
624

Description

### Environment

SaaS (https://sentry.io/)

### Version

_No response_

### Steps to Reproduce

Filtering on multiple `releases.*` keys in discover does not always provide expected results particularly in multi-project environments or projects with a lot of release objects. An example would be adding a search filter like `release.version:>1.0.0 release.build:>10 release.stage:adopted` to a Discover query.

### Expected Result

All releases that fit the above criteria.

### Actual Result

Empty results or a subset of the results.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.