Allow "Resolve in next release" to use those only in the same environment as the issue

[henrahmagix]

Problem Statement

I work with a Staging and a Production environment on the same codebase: Staging releases are made automatically for every git commit, so we name them by the git commit hash, whilst Production releases are made manually so we name them by the datetime e.g. 2024-12-03-1038.

As far as I'm aware, Sentry uses chronological ordering when Semantic Versioning is not detected. This part works great for us because we create releases sequentially and never make backport releases.

However, using "Resolve in the next release" on an issue in the Production environment ends up marking it as resolved when the next Staging release is created. This is incorrect for us: the issue occurred in Production, so we only want it to be resolved by a Production release.

Can it be possible please to ensure issues marked as resolved in an upcoming release, are only resolved by those appearing in the same environment as the issue?

Thanks in advance, Henry ☺

P.S. Semantic Versioning doesn't work for us unfortunately

Solution Brainstorm

• add a project configuration option to separate releases by their environment
• use that option when "Resolve in the next release" option is chosen on an issue

Product Area

Issues

[getsantry[bot]]

Auto-routing to @getsentry/product-owners-issues for triage ⏲️

[scttcper]

@henrahmagix thanks for writing in that makes sense, I've added this to our backlog