Triaging an issue means setting all the appropriate fields on it.
Set required labels
| Prefix | Required count | Notes |
|---|---|---|
work: |
1+ | All work: design issues should also be marked restricted: design team because only the design team can currently work on those. |
type: |
1 | |
status: |
1 | Should not be status: triage |
Set optional labels
Scan through the full labels list and apply other labels as necessary. Learn more about the meaning of all our labels.
Verify Project and fields
Set the Project to “Mathesar”.
Within the project, ensure that the status, priority, and work fields are set.
The project is only accessible to Team members, but all relevant information (such as status, priority, and milestone) should be available on individual issues. We will make this project public as soon as GitHub supports it.
Set milestone
If an issue is directly associated with a feature, put it in the milestone for that feature. Otherwise, put it in a “General Improvements” milestone according to priority. More urgent issues should go in this month’s milestone, otherwise put it in a milestone in the next couple of months.
If you don’t know what milestone to put something in, talk to Kriti.
Do not create any new milestones.
The list of available labels and milestones should only be changed in the mathesar repo. They are synced every day to the other repos related to the project using this GitHub action.