Skip to content

Proccess & tooling to triage issues #280

@jlewi

Description

@jlewi

We need a process and tools to triage GitHub issues.

Here's my initial proposal

The following needs to be true for an issue to be considered triaged

  • It has one the labels ("bug", "question", "enhancement")
  • It has a priority
  • If its P0/P1 it should be added to a kanban board
  • It has at least one "area" label

I will create a simple script that iterates over our issues and does the following

  1. Adds untriaged issues to a project used for triaging issues

    • I think a project is better than a label because we can potentially use cards to keep track of an issue; e.g. if there is some question about an issue and it needs to be discussed at the community meeting
  2. Add a comment on the issue explaining what criterion are missing for the issue to be considered triaged

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      pFad - Phonifier reborn

      Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

      Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


      Alternative Proxies:

      Alternative Proxy

      pFad Proxy

      pFad v3 Proxy

      pFad v4 Proxy