Skip to content

Raise the private triage yellow threshold #43

Description

@abstractj

Description

Problem: Private Triage turns yellow at 1. Any team with even a single private issue still in triage sees yellow. Having one issue in triage at any given time is just normal workflow, not a warning sign. The only way to reach green is zero issues in triage — a state that's practically unreachable for any team receiving ongoing reports. That can be frustrating when teams feel they're never able to catch up.

There's also no way to pause the clock when we're waiting on the reporter. Sometimes triage is done but the report is incomplete — we need more information or a reproducer before we can move forward. Once status/needs-info is assigned, the issue is blocked on the reporter's timeline, not ours. Reporters can take a week or more to respond, and that time shouldn't count against the team.

Proposal: Raise the yellow threshold so that normal triage workflow doesn't trigger a warning and green is actually reachable. Additionally, reset the triage counter when status/needs-info is assigned, and restart it when the label is removed.

Value Proposition

A yellow that's always on becomes noise. Raising the threshold keeps the indicator meaningful.

Goals

  • Raise the yellow threshold so normal triage workflow doesn't trigger a warning
  • Make green a reachable state for teams keeping up with their workload
  • Pause the triage counter while status/needs-info is assigned, restart it when the label is removed

Discussion

No response

Motivation

No response

Details

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/enhancementCategorizes an issue related to an enhancementpriority/importantMust be worked on very soon

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions