feat(releases): allow resolving in an upcoming release in the ui #76377
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
the
Scope: Frontend
sentaur-athena
added
the
Trigger: getsentry tests
scttcper
approved these changes
Aug 29, 2024
|
PR reverted: ceb1d49 |
mifu67
pushed a commit
that referenced
this pull request
Sep 3, 2024
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Now that the backend for resolving in an upcoming release is now ungated as of this PR, we can do the same in the UI. This feature is relatively low risk to just roll out to everyone because not many people will use it an it's well validated at Sentry (it was enabled while I was still a full time empoyee, lol).
I'm also going to update the docs for this new feature.