Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

docs: Update triaging docs #12669

Merged
merged 4 commits into from
Jun 27, 2024
Merged

docs: Update triaging docs #12669

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
597ad11
docs: Update triaging docs
mydea Jun 27, 2024
6ece31d
Apply suggestions from code review
mydea Jun 27, 2024
14939ac
Update docs/triaging.md
mydea Jun 27, 2024
1d15499
small tweak
mydea Jun 27, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions docs/triaging.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -43,6 +43,15 @@ categorize the issue as soon as possible. If an issue is hard to fix, an edge ca
reply and put the issue in backlog. You may also encourage the user to contribute a PR themselves if we are unlikely to
find time to resolve the issue ourselves anytime soon.

Additionally, triaging does not have to happen in one sitting. If you've investigated a reasonable amount of time into
mydea marked this conversation as resolved.
Show resolved Hide resolved
triaging an issue, but have not yet found the root cause/a solution, you can always post an update in the issue about
what you've tried so far (and what worked/didn't work), and continue looking into the issue later/on another day. This
depends on the severity of the issue, of course - if something appears to be a critical issue potentially affecting lots
mydea marked this conversation as resolved.
Show resolved Hide resolved
of users, we should prioritise fixing it even if it takes longer.

If a ticket is in the Web SDK triaging queue, but should be handled by another team (e.g. Replay, Feedback, Profiling),
feel free to ping members of that team in a respective Slack channel to please take a look at the issue.
mydea marked this conversation as resolved.
Show resolved Hide resolved

### (Sentry Employees) How & when should I triage issues?

Ideally, you can take some time every day in the morning to look over the triage queue and identify issues that you can
Expand Down
Loading