getsentry / getsentry/sentry

"resolved in the next release" not working as expected

Open
#88,976 33 comments 1 reaction 1 assignee Claimed by @cmanallen View on GitHub
Releases
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
22h 21m
Merged PRs (30d)
586

Description

### Environment

SaaS ([https://sentry.io/]())

### Steps to Reproduce

Customer is experiencing this issue with their iOS project, currently using fastlane plugin and verified correct semantic versioning per our [docs]().

Try to select "resolved in next release" for an issue from the latest release version for say version 4.6.1 (5)

### Expected Result

After selecting "resolved in next release" for an issue in version 4.6.1 (5) for the activity feed to show that it has been set as resolved in releases "greater than 4.6.1 (5)".

### Actual Result

Instead the activity feed shows that it has been set as resolved in releases "greater than 4.6.1 (2)" which is the wrong release.

This then means that the next time this issue occurs in 4.6.1 (5) it is immediately marked as a regression, which is correct since the "resolved in next release" version is incorrect at 4.6.1 (2).

Sentry appears to recognize that 4.6.1 (5) is > than 4.6.1 (2) because it is re-opening the issue, it just doesn't seem to be able to pick the right one when marking "resolved in next release".

Example links and additional details in internal ticket [#148963]()

Image

### Product Area

Releases

### 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.