You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: ISSUE_TRIAGE.md
+10-3Lines changed: 10 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,12 +2,13 @@
2
2
These are the procedures and guidelines on how issues are triaged in this repo by the maintainers.
3
3
4
4
## General
5
-
*Most issues must be tagged with **enhancement**or **bug**.
6
-
* Issues may be tagged with what it relates to (**backend**, **frontend**, **agent quality**, etc.).
5
+
*All issues must be tagged with **enhancement**, **bug**or **troubleshooting/help**.
6
+
* Issues may be tagged with what it relates to (**agent quality**, **frontend**, **resolver**, etc.).
7
7
8
8
## Severity
9
9
***Low**: Minor issues or affecting single user.
10
10
***Medium**: Affecting multiple users.
11
+
***High**: High visibility issues or affecting many users.
11
12
***Critical**: Affecting all users or potential security issues.
12
13
13
14
## Effort
@@ -18,8 +19,14 @@ These are the procedures and guidelines on how issues are triaged in this repo b
18
19
19
20
## Not Enough Information
20
21
* User is asked to provide more information (logs, how to reproduce, etc.) when the issue is not clear.
21
-
* If an issue is unclear and the author does not provide more information or respond to a request, the issue may be closed as **not planned** (Usually after a week).
22
+
* If an issue is unclear and the author does not provide more information or respond to a request,
23
+
the issue may be closed as **not planned** (Usually after a week).
22
24
23
25
## Multiple Requests/Fixes in One Issue
24
26
* These issues will be narrowed down to one request/fix so the issue is more easily tracked and fixed.
25
27
* Issues may be broken down into multiple issues if required.
28
+
29
+
## Stale and Auto Closures
30
+
* In order to keep a maintainable backlog, issues that have no activity within 30 days are automatically marked as **Stale**.
31
+
* If issues marked as **Stale** continue to have no activity for 7 more days, they will automatically be closed as not planned.
32
+
* Issues may be reopened by maintainers if deemed important.
0 commit comments