Issues search: Support AND/OR operators and wildcards for firstRelease filter
- Dominant language
- Python
- Stars
- 44.8k
- Forks
- 4.9k
- Avg merge
- 21h 10m
- Merged PRs (30d)
- 635
Description
### Problem Statement
When trying to filter issues by `firstRelease` in the Issues view, there's no way to:
1. Use wildcards (e.g., `firstRelease:com.example@1.2.*`)
2. Use boolean operators (AND/OR) to match multiple releases
This makes it difficult to answer questions like "show me all new issues introduced in releases 1.2.0 OR 1.2.1".
### Current Behavior
**Issues Search:**
- `firstRelease` filter works for exact matches
- Attempting to use `AND` or `OR` operators results in error: *"Boolean statements containing 'OR' or 'AND' are not supported in this search"*
- Wildcards do not work
**Discover:**
- Supports `OR` operator for `release` field (e.g., `release is X or release is Y`)
- However, `firstRelease` is **not available** as a queryable field in Discover
- This means filtering by `release` in Discover returns events from issues that may have existed prior to those releases, not just issues
*introduced* in those releases
### Expected Behavior
One of the following:
1. Support `OR` operator in Issues search for `firstRelease` (e.g., `firstRelease:X OR firstRelease:Y`)
2. Support wildcards in Issues search for `firstRelease` (e.g., `firstRelease:com.example@1.2.*`)
3. Add `firstRelease` as a queryable field in Discover
### Use Case
As a mobile developer, I want to see all **new issues introduced** across a range of related releases (e.g., 1.2.0 and 1.2.1) to assess the impact
of a feature rollout. Currently, I have to:
- Run separate queries for each release version
- Manually combine the results
- Or use Discover with `release` filter, which includes issues that existed before those releases
### Screenshots
*[Screenshots available - redacted for privacy]*
**Observed errors:**
- "Boolean statements containing 'OR' or 'AND' are not supported in this search"
- "The OR operator is not allowed in this search"
### Environment
- Sentry SaaS
- Project: Android
Contributor guide
Research direction
Start by tracing how the Issues search handles the firstRelease filter and how Discover defines queryable fields. Compare the existing release field support for OR and wildcards, then determine which of the three expected behaviors is feasible and verify that searches return only issues introduced in the selected releases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- search
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100