-
-
Notifications
You must be signed in to change notification settings - Fork 112
Cataloging Issues
lajbel edited this page Jul 27, 2026
·
4 revisions
When we catch new issues, we will do the following process:
In order to correctly catalog an issue, we will use the following guidelines for the different fields:
- Labels, Type: This fields are populated by the issue templates. Reviewer must check if all is filled correctly, and update if needed.
- Priority: The reviewer must fill this as Urgent, High, Medium, Low depending on how urgent for the engine to fix these bugs are, so they will be taken as maximum priority in case of Urgent, and different orders of priority from High to Low.
- Effort: The reviewer must use their best criteria to catalog how ammount of effort a task seems to have, this is not determining the time for performing the task. but it is a good first review point.
- Project: Always Issue Tracking
- *Asignee: If there's a PR, put PR owner as asiggne, if not leave it blank for lajbel's assignation.
- Relationships
