Environment
SaaS (https://sentry.io/)
Steps to Reproduce
- Use a project that has more than 100 releases.
- On an issue, click the Resolve dropdown → "Another existing release…".
- In the version picker, search for a release that is NOT among the 100 most recent (one that only appears via search, not in the default list).
- Click the release in the search results to select it.
Expected Result
The release stays selected and is shown in the version field, so the issue can be resolved in that release.
Actual Result
The version field immediately reverts to "Version: None" after the release is selected, so it looks like the selection didn't take. It only happens for releases outside the 100 most recent (i.e. ones reachable only through search); releases that appear in the default list select and stick normally.
This looks like a regression from the release-picker rework in #104565 (#104565), the searched release appears to drop out of the dropdown's option list once it's selected, leaving the field showing "None". Screenshots and the affected org/issue are in the linked Linear ticket.
Product Area
Issues
Link
No response
DSN
No response
Version
No response
Environment
SaaS (https://sentry.io/)
Steps to Reproduce
Expected Result
The release stays selected and is shown in the version field, so the issue can be resolved in that release.
Actual Result
The version field immediately reverts to "Version: None" after the release is selected, so it looks like the selection didn't take. It only happens for releases outside the 100 most recent (i.e. ones reachable only through search); releases that appear in the default list select and stick normally.
This looks like a regression from the release-picker rework in #104565 (#104565), the searched release appears to drop out of the dropdown's option list once it's selected, leaving the field showing "None". Screenshots and the affected org/issue are in the linked Linear ticket.
Product Area
Issues
Link
No response
DSN
No response
Version
No response