Triaged
Built for GitHub Issues

Every new issue, triaged on arrival.

Link a repository and tell Triaged which labels you use. Each new issue is assessed and gets the right priority label within seconds, so your team starts with the work that matters.

See pricing

Works with the labels you already use.

acme/api/Issues4 open
  • Heap overflow when parsing chunked responses
    priority: critical#4812 · by Triaged
    91
  • Login blocked after upgrading to 4.2
    priority: high#4810 · by Triaged
    72
  • Export ignores the selected time zone
    priority: medium#4807 · by Triaged
    48
  • Typo in the configuration guide
    priority: low#4803 · by Triaged
    12

How it works

Set up once. Every issue after that is handled.

  1. 01

    Subscribe

    Pick a plan. Your account and billing live in one place.

  2. 02

    Link a repository

    Connect GitHub, choose a repository and name the labels you already use.

  3. 03

    Issues arrive labeled

    Every new issue is scored for impact, urgency and readiness, then labeled.

Scoring

A transparent score, not a black box.

Three independent scores are combined into a priority from 0 to 100, then mapped to one of four bands.

Resistant to manipulation. Issues are treated as evidence, never as instructions, so text inside a report can't change its own score.

Weights

Impact50%
The concrete consequence for an affected user.
Urgency35%
Evidence of time pressure and ongoing harm.
Readiness15%
How clearly the work can be done and verified.

Bands

Low
0–34
Medium
35–59
High
60–79
Critical
80–100

Stop sorting issues by hand.

Link your first repository in a couple of minutes. Existing open issues can be prioritized too.