Issue
I want to know why an issue resolved with a commit message such as Fixes PROJECT-123 accepts new events but does not change status to Regressed.
Applies To
All SaaS Customers and Self-Hosted Users
Resolve via commit / pull request
Resolution
Sentry marks a commit-resolved issue as Regressed only when the fixing commit is in a release, and a later event arrives from a newer release.
Resolving with Fixes <ISSUE-ID> does not use plain Resolve. Sentry references the commit when it sees the message, then resolves the issue in the release that contains that commit. New events must include a release newer than that resolving release (by semver, or by release date if you are not using semver). Events with no release do not trigger Regressed.
To fix this:
Associate the fixing commit (or PR merge commit) with a release.
Set the same release in the SDK so new events carry a release value.
If you squash-merge, put
fixes <ISSUE-ID>in the pull request title or description so the merge commit in the release is what Sentry associates.
For more information, see Resolve Issues by Commit and Resolved in a Commit.