How do I specify that a Sentry issue is resolved in the next version for a specific environment?

### Environment

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

### What are you trying to accomplish?

There are times when a Sentry issue has been fixed in an upcoming release but we're not sure which "Resolve In".

The issue is that the only options we're given are "The next release", "The current release" (which I assume is the last release to be detected for this project), "Another existing release", and "A commit".

We have four different environments configured for our project, development, sandbox, QA, and production. We primarily monitor the production environment we use the other environments for testing and monitor that the fixes pushed out are no longer causing Sentry issues.

If I have an Issue and I know that it is fixed in the upcoming release but it is not yet merged into any of the other environments, how can mark it as resolved and not have it keep showing up?

Ideally I'd like to have an option in the "Resolved In" dropdown for **"The next production release"** or something along those lines to specify the environment. I know for a fact that the issue will be fixed in the next production release but I don't know when it'll make it through the other releases.

If I choose "The next release" as it is right now, it seems to assume it'll be fixed in the next release ON ANY ENVIRONMENT.

### How are you getting stuck?

The Sentry issue keeps showing up as a regression.

### Where in the product are you?

Issues

### Link

_No response_

### DSN

_No response_

### Version

24.11.2