Limit Issues list to recent releases or Support Last N Release based Filtering

[eric]

Problem Statement

I want to view my Issues that have impacted releases that happened in the last few weeks or just the last few releases.

I can't seem to find a query to do that. Instead I have to go to the Releases view and click on the issues for each of the recent releases.

Solution Brainstorm

No response

[getsentry-release]

Routing to @getsentry/support for triage. ⏲️

[kerenkhatiwada]

Hello @eric

Please see the searchable release properties here. You can search these properties both in the Issues tab and in Discover.

[eric]

What is the query to say "last 5 release" or "all releases in the last 2 weeks"?

[kerenkhatiwada]

Unfortunately, there isn't a query to specifically achieve the above. However, you may find it helpful to search with the firstRelease key and searching multiple values for the release key. You can also use a search like release.version:>backend@22.11 if you use semver.

[eric]

I’ve asked this question of support via email, was directed to the page on the help site that did not in fact help me. I asked for clarification and was told what I wanted to do wasn’t possible.

I then went here and submitted a feature request. I was then forwarded here to support, who directed me to the page on the help site that did not help me. I’ve now been told that what I want to do isn’t possible.

How do I submit a feature request to have the thing that would be very helpful to me added?

[kerenkhatiwada]

I see, thank you for the additional info. I'll route this to the team as a feature request.

[getsentry-release]

Routing to @getsentry/visibility for triage. ⏲️

[getsentry-release]

Routing to @getsentry/workflow for triage. ⏲️

[Dhrumil-Sentry]

Hi @eric Sorry for your experience

What is the query to say "last 5 release" or "all releases in the last 2 weeks"?

Currently, there is no way to query issues in this manner. This is already in our backlog and we will update this thread once we prioritize this feature.

Could you also please let us know why a semver-based search like release.version:>backend@22.11 does not work for you?

[eric]

Could you also please let us know why a semver-based search like release.version:>backend@22.11 does not work for you?

Because hard-coding a version means that I can't save a query that is always up-to-date with the recent useful issues.

It's not friendly to have to go look at what the most recent releases were, figure out the version number and then make a manual query when this is something that the system can answer automatically.

[connorjclark]

Could you also please let us know why a semver-based search like release.version:>backend@22.11 does not work for you?

In my case, it's because we don't use semver, at least not for our nightly releases (just nightly-YYYY-MM-DD). Given semver filtering works today but not release date, I'll probably change this. Would something like this work for your semver precedence logic used in filtering?

2.55-1.nightly-2023-02-01

If I'm understand the semver spec correctly, prelease tags should get sorted component-wise left-to-right (numerically if a number, else lexically), hence 1.nightly instead of nightly because otherwise nightly < alpha (or beta, or rc, etc).

To be clear, I'm asking if queries like these should be expected to work:

• release.version:>=2.55-1.nightly-2023-02-01
• release.version:>=2.55-1.nightly-2023
• etc.

Of course, last 3 releases or whatever would be a lot simpler.

[getsantry]

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

[Dhrumil-Sentry]

@connorjclark Sorry for the very late reply, completely missed this comment

To be clear, I'm asking if queries like these should be expected to work:

release.version:>=2.55-1.nightly-2023-02-01
release.version:>=2.55-1.nightly-2023
etc.

@scttcper Do you OTOH if such a search would work? I think its not supported.

Of course, last 3 releases or whatever would be a lot simpler.

@connorjclark This is a very valid ask and I've added this to our backlog, will keep this issue updated once we have this

[eric]

I still really want a way to create a saved filter that is always up-to-date that returns issues that have happened in the last "N" releases that doesn't require me to constantly update the version number.

I have an iOS and tvOS app and I would like a view that isn't showing me crashers for people who are stuck on old versions because they are not able to update their OS versions.

[dcramer]

My feedback here:

We should be providing something akin to release:latest that is a virtual query, that can then be adjusted on-the-fly via settings.

It should probably have two modes of operation:

1. Last N releases
2. Release within N time interval

Possibly a combination of the two.

"Consider a release part of the latest if it matches any of these conditions"