Maintenance ticket filing cannot apply Status/Priority labels on filed issues #213

New issue

Closed

opened 2026-06-15 06:06:08 +00:00 by igor · 1 comment

igor commented

2026-06-15 06:06:08 +00:00

Collaborator

Diagnosis

After filing each maintenance triage ticket, the harness fails to apply its triage-stamp labels (Status/Need More Info, Priority/{Low,Medium}). The ticket is filed but lands unlabeled, defeating the human triage workflow. This recurs across four repos in the window (ageofcombat.com #4, idolidle.com #4, knowthetable.com #4, snail.io #10); joshing.you #55 filed without the warning, suggesting the labels simply don't exist on the affected repos and the harness assumes they do.

Evidence

Jun 15 00:21:54 igor tick.sh[2912702]: [agent] warning: could not apply 'Status/Need More Info' on #4 (joshtronic/ageofcombat.com)
Jun 15 00:21:54 igor tick.sh[2912702]: [agent] warning: could not apply 'Priority/Low' on #4 (joshtronic/ageofcombat.com)
Jun 15 00:27:04 igor tick.sh[2912702]: [agent] warning: could not apply 'Status/Need More Info' on #4 (joshtronic/idolidle.com)
Jun 15 00:27:04 igor tick.sh[2912702]: [agent] warning: could not apply 'Priority/Medium' on #4 (joshtronic/idolidle.com)
Jun 15 00:32:14 igor tick.sh[2912702]: [agent] warning: could not apply 'Status/Need More Info' on #4 (joshtronic/knowthetable.com)
Jun 15 00:34:23 igor tick.sh[2912702]: [agent] warning: could not apply 'Status/Need More Info' on #10 (joshtronic/snail.io)
Jun 15 00:34:24 igor tick.sh[2912702]: [agent] warning: could not apply 'Priority/Low' on #10 (joshtronic/snail.io)

Fixed looks like

The harness either ensures the required labels exist on each target repo before applying (create-if-missing) or downgrades gracefully without a warning, so maintenance tickets land with their intended Status/Priority stamps.

service: agent.service
severity: low
window: 2026-06-15 00:00-01:00 (filed by the nightly logwatch pass)

## Diagnosis After filing each maintenance triage ticket, the harness fails to apply its triage-stamp labels (`Status/Need More Info`, `Priority/{Low,Medium}`). The ticket is filed but lands unlabeled, defeating the human triage workflow. This recurs across four repos in the window (ageofcombat.com #4, idolidle.com #4, knowthetable.com #4, snail.io #10); joshing.you #55 filed without the warning, suggesting the labels simply don't exist on the affected repos and the harness assumes they do. ## Evidence ``` Jun 15 00:21:54 igor tick.sh[2912702]: [agent] warning: could not apply 'Status/Need More Info' on #4 (joshtronic/ageofcombat.com) Jun 15 00:21:54 igor tick.sh[2912702]: [agent] warning: could not apply 'Priority/Low' on #4 (joshtronic/ageofcombat.com) Jun 15 00:27:04 igor tick.sh[2912702]: [agent] warning: could not apply 'Status/Need More Info' on #4 (joshtronic/idolidle.com) Jun 15 00:27:04 igor tick.sh[2912702]: [agent] warning: could not apply 'Priority/Medium' on #4 (joshtronic/idolidle.com) Jun 15 00:32:14 igor tick.sh[2912702]: [agent] warning: could not apply 'Status/Need More Info' on #4 (joshtronic/knowthetable.com) Jun 15 00:34:23 igor tick.sh[2912702]: [agent] warning: could not apply 'Status/Need More Info' on #10 (joshtronic/snail.io) Jun 15 00:34:24 igor tick.sh[2912702]: [agent] warning: could not apply 'Priority/Low' on #10 (joshtronic/snail.io) ``` ## Fixed looks like The harness either ensures the required labels exist on each target repo before applying (create-if-missing) or downgrades gracefully without a warning, so maintenance tickets land with their intended Status/Priority stamps. --- service: agent.service severity: low window: 2026-06-15 00:00-01:00 (filed by the nightly logwatch pass)