Skip to content

Adding consistent labels to toolkit repositories to help manage issues #44

@chanskw

Description

@chanskw

Issues in Github is a flat list of work items. There is no concept of priority, severity, and status like other systems. When this list is small, it may be easy to prioritize and manage, but can quickly get out-of-hand as the repositories grow. We need a way to help us manage the issues.

I am not suggesting that we need these for all repositories, but should be considered by Repository Committers based on how they want to manage issues.

Here's a list of proposed labels to help with issues management:

Category Labels

Task
Bug
Feature
Discussion - I think this discussion category is helpful as we have been using issues for a lot of discussions.
Idea - anyone who wants to propose an idea, can use this.  Different from feature where idea is a proposal / suggestion.  Features may result in actual coding being done.  We may want to use this tag for repository proposal to separate them from project admin discussions.

Priority Label

HIGH
LOW

If unassigned, it is by default medium priority. Allow developers to prioritize work.

Severity Label
BLOCKING
MAJOR
NORMAL
MINOR

If unassigned, it is by default normal. Allow issue reporter to let us know how bad the problem is.

Status Labels

triaged
in-progress
fixed
invalid (not-reproducible, working as designed, etc.)
need feedback 

With the labels, we can then create queries to help us look at issues that we want. With no status label, issue is new and not-triaged.

Thoughts?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions