# Ticket: Pi feedback and issue tracking system

## Metadata
- Type: Ticket
- Status: Planned
- Project: Pi / Nimrod
- Created: 2026-05-17
- Updated: 2026-05-17
- Priority: High

## Goal

Create a lightweight system for capturing user feedback, bugs, pain points, and improvement requests about the whole Pi/Nimrod assistant system, then converting them into trackable fixes.

## Why

Pi is becoming an operational assistant platform. As it grows, feedback needs to be captured reliably instead of getting lost in chat. A feedback loop will help improve usability, safety, reliability, and user trust over time.

## Scope

Included:
- Define where feedback is captured initially.
- Define categories such as bug, annoyance, missing capability, safety concern, workflow friction, documentation issue, and feature request.
- Create a triage workflow to convert feedback into tickets/specs.
- Add a status model for reported issues.
- Support capture from Nextcloud Talk via the existing `pi ...` request queue where practical.
- Document the workflow in the repo operating docs.

Not included:
- Public issue tracker exposure.
- Automated code changes without review.
- Complex multi-user product management tooling in the first version.

## Acceptance Criteria

This ticket is done when:
- [ ] A feedback intake file or folder exists.
- [ ] A feedback/issue template exists.
- [ ] A triage process is documented.
- [ ] Feedback can be linked to tickets/specs/fixes.
- [ ] At least one sample feedback item is captured and triaged.
- [ ] Nextcloud Talk instructions explain how to submit Pi feedback.

## Questions

- Should feedback live in `feedback/`, `inbox/`, `tickets/`, or a Nextcloud-facing file first?
- What status labels should we use for feedback items?
- Should the Talk bot get a dedicated `feedback ...` command?

## Plan / Next Actions

- [ ] Design a minimal feedback schema.
- [ ] Create feedback template and intake location.
- [ ] Add a triage checklist.
- [ ] Update Talk assistant help/runbook if adding a `feedback` command.
- [ ] Test with one real feedback item.

## 2026-05-17 Spec Advancement

Confidence level: high that this should be the first Pi upgrade after request import, because it improves every future iteration.

Decisions now stable:
- Feedback should be lightweight Markdown-first and repo-native.
- Feedback should be capturable from Talk using either a future `feedback ...` command or current `pi ...` queue.
- Feedback items should triage into tickets/specs rather than becoming an unbounded list.

Proposed MVP spec:
- Create `feedback/README.md` and `feedback/inbox.md`.
- Add `docs/templates/feedback-template.md`.
- Use statuses: `new`, `triaged`, `planned`, `fixed`, `wontfix`, `deferred`.
- Use categories: bug, friction, missing capability, safety concern, documentation, workflow, idea.
- Weekly or session-start triage converts items into tickets or closes them with notes.

Updated next actions:
- [ ] Create the feedback folder and template.
- [ ] Add a triage checklist to `docs/operating-system.md` or a feedback README.
- [ ] Add a Talk help note: use `pi feedback: ...` until a dedicated command exists.

## Notes

- User requested this as Pi upgrade item 1 on 2026-05-17.