getsentry / getsentry/sentry

"Resolved in the next release" does not consider the current release

Open
#78,325 4 comments 0 reactions 0 assignees View on GitHub
Bug
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
22h 21m
Merged PRs (30d)
586

Description

### Environment

self-hosted (https://develop.sentry.dev/self-hosted/)

### Steps to Reproduce

- Open an issue which was last seen in an older release than the current
- Resolve the issue in the next release

### Expected Result

- Issue is marked as resolved in the release after the current

### Actual Result

- Issue is marked as resolved in the release after the latest the issue was seen in

![Image](https://github.com/user-attachments/assets/c2f26f72-a540-4988-884a-54ebfef27e2f)
![Image](https://github.com/user-attachments/assets/76bbeece-ea1b-4538-b117-6cf00fe11ae8)
![Image](https://github.com/user-attachments/assets/a8d89319-cc5e-410b-b388-3fcf8c66b472)

### Product Area

Issues

### Link

_No response_

### DSN

_No response_

### Version

_No response_

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.