fix(issue ownership): Clarify that groups with assignees are never reassigned #14840
Conversation
This file contains hidden or 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
…pt to reassign a group that already has an assignee
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
Bundle ReportChanges will decrease total bundle size by 15 bytes (-0.0%) ⬇️. This is within the configured threshold ✅ Detailed changes
Affected Assets, Files, and Routes:view changes for bundle: sentry-docs-client-array-pushAssets Changed:
view changes for bundle: sentry-docs-server-cjsAssets Changed:
|
JoshFerge
approved these changes
Sep 8, 2025
shashjar
added a commit
to getsentry/sentry
that referenced
this pull request
Sep 8, 2025
… not reassigned (#98750) Resolves [ID-227](https://linear.app/getsentry/issue/ID-227/issue-owners-are-not-reordered-when-rules-are-reordered). We determined the bug reported in the above issue to be intended behavior. If a group already has an assignee, our post-processing logic will never attempt to reassign it when new events come in, even if the cache has expired and/or the ownership rules have changed in the interim. This PR adds a test to capture this behavior. [A separate PR](getsentry/sentry-docs#14840) has been created to update the [Ownership Rules](https://docs.sentry.io/product/issues/ownership-rules/) documentation page in order to make this behavior more explicit to users.
shashjar
deleted the
id-227-update-ownership-rules-docs-issue-reassignment
branch
andrewshie-sentry
pushed a commit
to getsentry/sentry
that referenced
this pull request
Sep 9, 2025
… not reassigned (#98750) Resolves [ID-227](https://linear.app/getsentry/issue/ID-227/issue-owners-are-not-reordered-when-rules-are-reordered). We determined the bug reported in the above issue to be intended behavior. If a group already has an assignee, our post-processing logic will never attempt to reassign it when new events come in, even if the cache has expired and/or the ownership rules have changed in the interim. This PR adds a test to capture this behavior. [A separate PR](getsentry/sentry-docs#14840) has been created to update the [Ownership Rules](https://docs.sentry.io/product/issues/ownership-rules/) documentation page in order to make this behavior more explicit to users.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
Resolves ID-227.
Follow-up to this PR. Updates the Ownership Rules documentation to clarify the intended behavior. Our post processing logic will never attempt to reassign a group if an assignee already exists, even if the cache has expired and/or the ownership rules have changed in the interim.
IS YOUR CHANGE URGENT?
Help us prioritize incoming PRs by letting us know when the change needs to go live.
PRE-MERGE CHECKLIST
Make sure you've checked the following before merging your changes:
EXTRA RESOURCES