Description
When the assistant converts an inbound-feedback entry into a problem ticket, the full close-the-loop sequence should run automatically as part of the conversion; it does not — the assistant stops after creating the ticket and only performs the remaining steps after the user prompts.
The behaviour is channel-agnostic: some adopter projects receive feedback via GitHub issues reported upstream, others via a bespoke channel (e.g. a Firestore feedback collection), but the same close-the-loop steps apply regardless of channel. On conversion the assistant must, in the same pass and without a prompt: (a) update the source feedback entry's triage state to converted + link the problem ID, and (b) author the user-facing response the triage process calls for.
Symptoms
- Feedback entries stay unactioned after their conversion ticket exists — the read/write loop stays open on the write side.
- Submitters receive only a bare auto-status, never an authored acknowledgement.
- The user has to police the assistant to complete a documented, mandatory workflow.
Affected plugin / component
@windyroad/itil — feedback-conversion / triage flow (and the retrospective conversion path).
Fix direction
Make triage-state update + user response an automatic consequence of conversion, defined against a channel-agnostic feedback interface (GitHub-issue channel and bespoke channels alike).
Cross-reference
Reported from a downstream adopter; tracked locally as P162.
Versions
- Local plugin:
@windyroad/* (cache: itil 0.57.1)
- Claude Code CLI: 2.1.201 (Claude Code)
- Node: v22.17.1
- OS: Darwin 25.3.0 x86_64
Description
When the assistant converts an inbound-feedback entry into a problem ticket, the full close-the-loop sequence should run automatically as part of the conversion; it does not — the assistant stops after creating the ticket and only performs the remaining steps after the user prompts.
The behaviour is channel-agnostic: some adopter projects receive feedback via GitHub issues reported upstream, others via a bespoke channel (e.g. a Firestore feedback collection), but the same close-the-loop steps apply regardless of channel. On conversion the assistant must, in the same pass and without a prompt: (a) update the source feedback entry's triage state to converted + link the problem ID, and (b) author the user-facing response the triage process calls for.
Symptoms
Affected plugin / component
@windyroad/itil— feedback-conversion / triage flow (and the retrospective conversion path).Fix direction
Make triage-state update + user response an automatic consequence of conversion, defined against a channel-agnostic feedback interface (GitHub-issue channel and bespoke channels alike).
Cross-reference
Reported from a downstream adopter; tracked locally as P162.
Versions
@windyroad/*(cache: itil 0.57.1)