github/OpenHands
1
0
Fork 0
mirror of https://github.com/OpenHands/OpenHands.git synced 2025-12-26 05:48:36 +08:00
Code Issues Packages Projects Releases Wiki Activity

Updates to the ISSUE TRIAGE (#7043)

Browse Source
This commit is contained in:
mamoodi 2025-03-02 10:35:47 -05:00 committed by GitHub
parent 660d1d1e64
commit ff5d8094de
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 10 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
ISSUE_TRIAGE.md
View File

@ -2,12 +2,13 @@
These are the procedures and guidelines on how issues are triaged in this repo by the maintainers. These are the procedures and guidelines on how issues are triaged in this repo by the maintainers.
## General ## General
* Most issues must be tagged with **enhancement** or **bug**. * All issues must be tagged with **enhancement**, **bug** or **troubleshooting/help**.
* Issues may be tagged with what it relates to (**backend**, **frontend**, **agent quality**, etc.). * Issues may be tagged with what it relates to (**agent quality**, **frontend**, **resolver**, etc.).
## Severity ## Severity
* **Low**: Minor issues or affecting single user. * **Low**: Minor issues or affecting single user.
* **Medium**: Affecting multiple users. * **Medium**: Affecting multiple users.
* **High**: High visibility issues or affecting many users.
* **Critical**: Affecting all users or potential security issues. * **Critical**: Affecting all users or potential security issues.
## Effort ## Effort
@ -18,8 +19,14 @@ These are the procedures and guidelines on how issues are triaged in this repo b
## Not Enough Information ## Not Enough Information
* User is asked to provide more information (logs, how to reproduce, etc.) when the issue is not clear. * User is asked to provide more information (logs, how to reproduce, etc.) when the issue is not clear.
* 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). * 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).
## Multiple Requests/Fixes in One Issue ## Multiple Requests/Fixes in One Issue
* These issues will be narrowed down to one request/fix so the issue is more easily tracked and fixed. * These issues will be narrowed down to one request/fix so the issue is more easily tracked and fixed.
* Issues may be broken down into multiple issues if required. * Issues may be broken down into multiple issues if required.
## Stale and Auto Closures
* In order to keep a maintainable backlog, issues that have no activity within 30 days are automatically marked as **Stale**.
* If issues marked as **Stale** continue to have no activity for 7 more days, they will automatically be closed as not planned.
* Issues may be reopened by maintainers if deemed important.