getsentry / getsentry/sentry

Resolve Issue in The Next Deploy

Open
#67,830 7 comments 8 reactions 0 assignees View on GitHub
Feature
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
22h 21m
Merged PRs (30d)
586

Description

### Problem Statement

**Problem described by sentry developer**
"i do think we've done a poor job supporting semantic releases in other ways, people often ask for "resolved in next major/minor version" which "the next release" doesn't support".

I think resolving via the release with the Deploy tag could fix it.

**QuestionByCustomer:**
“How do I resolve an Issue for its release and have it not be a regression?” They're marking the the Issue as Resolved but it's for a Release that's in Prod, and that release doesn't have the fix yet. And so the Issue re-opens when the event occurs again.

**Question:** If the developer has a branch fix for the Issue, then they want to mark the Issue as ’resolved by the fix-branch', but the fix branch hasn’t been deployed yet because it’s a Mobile app and it takes some time to merge+build+deploy. And their Rlease for it hasn't been created either.

User says “[Resolve in Next Release](https://docs.sentry.io/product/releases/#resolved-in-the-next-release)” doesn’t work because he has many developers making releases and some are from local dev testing, it’s not truly the next Release in Prod. The other developers don’t have his fix so the Issue wil instantly become a regression.

User says none of the options dropdown work for him

User starts a feature/fix branch but does not set a new release value yet in Sentry.init(release:release) because "We're not explicitly setting the release in the Sentry init options. The release is just the default name of the current release we set up in our build script". Sounds like it doesn't get set till later in the cloud and CICD when it's getting closer to a real deployment.

Docs say to do "We recommend notifying Sentry about a new release before deploying it. " but he doesn't/can't for the above reason.

### Solution Brainstorm

Resolve Issue in The Next Deploy. I'm talking about the 'deploy' label that can go on a release. Having trouble finding the docs

https://docs.sentry.io/api/releases/create-a-new-deploy-for-an-organization/.
https://docs.sentry.io/product/releases/

found it

https://docs.sentry.io/product/cli/releases/#creating-deploys

### Product Area

Issues

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.