Skip to content

Separate triage columns by severity #45

@abstractj

Description

@abstractj

Description

Problem: Issues with no severity label default to the most aggressive deadline (2 business days, same as severity/important). The issue must already have status/triage to appear in this column, but if it's missing a severity/* label, it gets the fastest overdue clock. If someone files a private triage issue on Friday without adding a severity label, it shows as overdue by Wednesday.

Proposal: Split the private triage column into separate columns per severity — including one for missing severity — so each can have its own threshold.

Value Proposition

Different severities have different triage urgency. Separate columns give a clearer picture of where things stand without lumping everything into one bucket.

Goals

  • Add separate triage columns for each severity level plus a "missing severity" column
  • Set different overdue thresholds per column

Non-Goals

No response

Discussion

No response

Notes

Issues with no severity set could still be critical, so the missing-severity column should still encourage prompt labeling. Severity should be treated as fluid — set an initial estimate early and refine it later rather than treating it as a one-time decision.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions