issue create: apply a default priority label (P3) at filing time #161

New issue

Open

opened 2026-05-31 01:30:29 +00:00 by coilysiren · 0 comments

coilysiren commented

2026-05-31 01:30:29 +00:00

Owner

Problem

The backlog now runs priority-on-everything: every open issue carries a P0/P1/P2/P3 label (see the tooling-issue-prioritization skill). But that coverage was a one-time cascade. New issues are filed with no priority, so the backlog silently drifts back toward untiered, and the 5/15/30/50 ratio decays. Already saw ~10 untagged issues appear within a day of the pass.

Wanted: filing-time default

coily ops forgejo issue create should apply a default priority label at creation. Default to P3 (the someday/low default tier per the skill) so new captures land in the tail, not jump the queue. Allow override with a flag, e.g. --priority P1.

Ensure the target priority label exists in the repo (create on demand), then apply it - reuses the label-apply path from #159, so this depends on #159.
Resolve canonical repo path before the create+label (the org-split redirect swallows writes - see #549).

Alternative / complement: a sweep

If filing-time defaulting is too invasive, a periodic "untiered issues" sweep (fold into the daily backlog routine) that finds open issues with no P* label and defaults them to P3 keeps coverage at 100% without changing the create path. The two compose: default at create, sweep as backstop.

Why

Without one of these, priority-on-everything needs a manual re-cascade every so often. A filing-time default makes the system self-maintaining. See the tooling-issue-prioritization skill for the tier definitions and ratio.

## Problem The backlog now runs priority-on-everything: every open issue carries a `P0`/`P1`/`P2`/`P3` label (see the `tooling-issue-prioritization` skill). But that coverage was a one-time cascade. **New issues are filed with no priority**, so the backlog silently drifts back toward untiered, and the 5/15/30/50 ratio decays. Already saw ~10 untagged issues appear within a day of the pass. ## Wanted: filing-time default `coily ops forgejo issue create` should apply a default priority label at creation. Default to **`P3`** (the someday/low default tier per the skill) so new captures land in the tail, not jump the queue. Allow override with a flag, e.g. `--priority P1`. - Ensure the target priority label exists in the repo (create on demand), then apply it - reuses the label-apply path from #159, so this depends on #159. - Resolve canonical repo path before the create+label (the org-split redirect swallows writes - see #549). ## Alternative / complement: a sweep If filing-time defaulting is too invasive, a periodic "untiered issues" sweep (fold into the daily backlog routine) that finds open issues with no `P*` label and defaults them to `P3` keeps coverage at 100% without changing the create path. The two compose: default at create, sweep as backstop. ## Why Without one of these, priority-on-everything needs a manual re-cascade every so often. A filing-time default makes the system self-maintaining. See the `tooling-issue-prioritization` skill for the tier definitions and ratio.

coilysiren added the

label

2026-05-31 01:52:35 +00:00

coilysiren added

and removed

labels

2026-05-31 06:59:39 +00:00

No labels

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

coilyco-bridge/coily#161

No description provided.

Rows
Columns