Skip to content

Commit 3ad591f

Browse files
mrduncanbitsandfoxes
authored andcommitted
fix(issues): Clarify assignment caveat (#14078)
1 parent 5c6ed97 commit 3ad591f

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/product/issues/ownership-rules/index.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -165,7 +165,7 @@ You can automatically assign issues to their owners by enabling the "Auto-assign
165165

166166
![Select from dropdown to automatically assign issues to their owners.](./img/auto-assign-issue-owner.png)
167167

168-
If an issue has already been assigned manually, new events will not change the current assignee. If an issue has not been assigned and a new event has multiple owners, Sentry assigns it to the owner(s) from the last matching rule (regardless of the rule `type`).
168+
If an issue has been assigned manually in the past, new events will not change the current assignee. If an issue has not been assigned and a new event has multiple owners, Sentry assigns it to the owner(s) from the last matching rule (regardless of the rule `type`).
169169

170170
Please keep in mind that auto-assignment may be skipped if a project is creating too many new issues at a given time due to rate limits. We'll try to auto-assign it the next time an event comes in for those skipped issues. If you are encountering this limit with non-recurring issues, you may want to take a look at [issue grouping](/concepts/data-management/event-grouping/) strategies.
171171

0 commit comments

Comments
 (0)