[error-tracking] auto assign documentation #30011
Draft
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
ℹ️ Documentation Team ReviewNo documentation team review is required for this pull request. |
leomelki
force-pushed
the
leomelki/ERRORT-5248_auto-assign
branch
from
293df85 to
a97bcd2
Compare
Preview links (active after the
|
fdehau
reviewed
Jun 20, 2025
|
|
||
| ## Overview | ||
|
|
||
| Auto Assign helps teams quickly resolve issues by automatically assigning them to the most likely responsible developers. It uses [suspect commits][1] to identify developers who may have introduced issues, then assigns the issue directly to the developer who made those commits. When an issue is automatically assigned to a developer, they receive an immediate notification. |
There was a problem hiding this comment.
Suggested change
| Auto Assign helps teams quickly resolve issues by automatically assigning them to the most likely responsible developers. It uses [suspect commits][1] to identify developers who may have introduced issues, then assigns the issue directly to the developer who made those commits. When an issue is automatically assigned to a developer, they receive an immediate notification. | |
| Auto Assign automates triaging by assigning issues to the author of their [suspect commit][1]. |
| - Ensure [Source Code Integration][2] is enabled and setup. | ||
| - Install [the GitHub integration][3]. Make sure all requested permission is granted for the GitHub integration. | ||
|
|
||
| ### Ensure email consistency |
There was a problem hiding this comment.
make it a bullet point in the previous list and remove the second sentence that repeat the first one.
|
|
||
| When an error occurs, Auto Assign: | ||
|
|
||
| 1. Analyzes the stack trace to identify suspect commits |
There was a problem hiding this comment.
Suggested change
| 1. Analyzes the stack trace to identify suspect commits | |
| 1. Analyzes the stack trace to identify a suspect commit |
| ### Assignment management | ||
| You can view assigned developers directly within each issue in Datadog. If needed, manual reassignment is always possible to override the automatic assignment. | ||
|
|
||
| ## Benefits |
There was a problem hiding this comment.
same as in the other PR: a single sentence on why this is useful and it should be in the first paragraph
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.