Triaging Issues

Summary

How we triage (categorize) new issues.

An issue can be anything from github or something created by a team member as part of the weekly planning process.

Steps

1. Triage the task:
   • if the item is high priority
     • add tags.sprint.active (Private) label to the task
     • attempt repro immediately and assign an engineer for immediate investigation
   • add the appropriate tags.scope.{scope} (Private) to the task
     • Valid values can be found in the tags.scope.* hierarchy
     • This should match the hierarch of the note (i.e. task.lookup.blah)
   • add an approximate size to the tags.size field, if possible
   • if the item is a good crop candidate
     • add tags.crop (Private) to the task
     • respond with the following template in the issue (Private)
   • Other fields are non-essential and can be left blank
2. Upload the task to Airtable with this sop: Issues in Airtable

Examples

• Podsv2 Edit Config Command (Private)

Related

• Triage GitHub Issue (Private)

Next Steps

• update the following documents:
  • Triage (Private)
  • Monthly Triage (Private)

---

Backlinks

• Projects and Issues