work-items: probe org issue field for work status #7600
Description
Parent
Refs #7577 (Work-item status). Source: PLAN Phase 1 (owner sitting, complete), topic
poteto-review.
Depends on
- none (filed closed with its result)
Outcome
Recorded: an org single-select issue field can hold work-item status and a token with
issues: write can set it.
Decisions
- Q563 (owner Q592, Q593; GUIDE 123). GitHub reserves the name
status(creating it returned 422
"Name cannot have a reserved value"), so the org field isWork status: single-select, visibility
all, options needs-triage, needs-reporter-info, needs-owner-decision, needs-spec, agent-ready.
Origin: owner's sitting. - Probe issue test: Q563 issue-field probe (close after) #7553 was set to needs-spec, then agent-ready, through the issue-field-values API with
the owner's token; both writes succeeded; closed as not planned. - The Issue events API shows one
issue_field_addedevent with no values and no update record, so
lanes cannot read history from it: the status thread triggers on Actionsissues: field_added,
payloadchanges.issue_field_value.from, checked live on its first trigger run.
Key interfaces
Variation verdicts: "Work-item status storage: abstract now; tracker adapter; field where offered,
labels as fallback (Q563)."
Done when
- A
Probe result:comment carries the observations above, the API used and the date
2026-10-16 (posted at filing).
Out of scope
- The live
changes.issue_field_value.fromcheck (status thread's first trigger run).
Activity
kyle-sexton commentedon Oct 16, 2026
Probe result: Q563, 2026-10-16 (owner Q592, Q593).
POST /orgs/melodic-software/issue-fieldswith namestatusreturned 422 "Name cannot have a reserved value". The org field was created asWork status: id 48484079, single-select, visibility all, options needs-triage, needs-reporter-info, needs-owner-decision, needs-spec, agent-ready.POST repos/melodic-software/claude-code-plugins/issues/7553/issue-field-valueswith the owner's user token. Both writes succeeded; test: Q563 issue-field probe (close after) #7553 closed as not planned.issue_field_addedevent, with no values and no record of the update; lanes cannot read history from it.on: issues: types: [field_added](docs.github.com, events that trigger workflows,issues); payloadchanges.issue_field_value.fromper the OpenAPIwebhook-issues-field-addedschema. Not checked live: no webhook exists and none was created, since it would send data to a third party. The status thread's first trigger run logs and asserts it.Work status.github-actions commentedon Oct 16, 2026
Thanks for the report. Automated triage handed this issue to a maintainer.
Proposed work class: work-class: read-only
Basis: automated intake triage; a maintainer confirms or changes it.
Automated triage. A maintainer reviews it.