Triage GitHub Issue

Summary

How incoming github issues are triaged

Steps

Go through issues with the label status.triage-needed (query)
For issues, first check if it is valid:
- Check if issue is a Duplicated to an existing bug/epic. If so, add the duplicate label and close the issue
- Check if issue "needs-info" because we need more details to figure out what the issue is. If so, add what info is needed and add the label.
- Check if the issue is a valid issue (eg. describes a bug or requests for new functionality) vs a support question
If the issue is valid
- make sure the issue has the following labels:
  - #scope (Private)
  - type
  - size
    - NOTE: if unsure about size, ping @DendronTeam
- depending on priority, the issue can go into one of the following buckets
  - add #sprint.active (Private) label to the task
    - if item is high priority, repro immediately and assign an engineer and tag to current milestone for immediate investigation
  - add #sprint.backlog (Private) to the task
    - if the item is a valid feature request or non-urgent bug
  - add #kind.crop (Private) to the task
    - if the item is a good crop candidate, add it as a crop
    - respond with the following template in the issue (Private)
  - add #kind.icebox (Private) to the task
    - if the item is not something we plan on working on for the current year
- create a task note inside the task from github (Private) section of this week's oncall note if it is a #type.bug (Private)
  - follow process in Creating New Issues (Private)
  - make sure to fill out the issue (Private) field with the link to the github issue
  - add the same #sprint (Private) and #kind (Private) tags to the task as you did to the github issue
- export the task
If the issue is a bug, add the following steps: Bug
For all cases,
- leave a comment in the ticket acknowledging that we have received it and communicate the next steps to the user
- remove the status.triage-needed label from the issue

Children

Summary

Steps