Cataloging Issues
This document explains the proccess to be followed by reviewers a new issue is created, in order to correctly classificate them.
| Concept | Meaning |
|---|---|
| Reviewer | The person performing the task |
| Contributor | The issue opener |
The issue attributes are found in GitHub in the sidebar of an issue:
There's 9 Attributes, but only three are filled by reviewer: Labels, Type, Fields.
- Labels & Type: This fields are populated by the issue templates. Reviewer must check if all is filled correctly, and update if needed.
-
Fields:
- 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.
