Summary
Operations teammates can now add and update internal notes on an order. Notes persist as part of the order record, providing internal context for follow-up work.
Ticket: Assignment 2 - Internal order notes
What changed
Added persistent internal notes to order records and existing database initialization.
Added an employee-only notes API with empty-note and 1,000-character validation.
Added an Internal notes panel to order details with save feedback and audit events.
How to test
bun run check
bun run test
bun run build:web
Manual checks:
Sign in as an employee, open an order, add a note, and verify it displays successfully.
Refresh the page and confirm the note persists.
Update the note and confirm an audit event appears.
Confirm empty notes cannot be saved and notes are limited to 1,000 characters.
Screenshots or recordings
Attach a screenshot or recording of the Internal notes panel.
Risks / follow-ups
Saving notes replaces the existing note instead of maintaining a threaded history.
Simultaneous edits could overwrite another employee’s changes.
PR checklist
change is scoped to one ticket or one small reviewable concern
acceptance criteria were checked
code follows CONTRIBUTING.md
no unrelated refactor is mixed in
debug code and temporary logs are removed
relevant automated checks were run locally
changed behavior was manually tested when needed
known risks or follow-ups are called out
Summary
Operations teammates can now add and update internal notes on an order. Notes persist as part of the order record, providing internal context for follow-up work.
- Ticket: Assignment 2 - Internal order notes
What changed
- Added persistent internal notes to order records and existing database initialization.
- Added an employee-only notes API with empty-note and 1,000-character validation.
- Added an Internal notes panel to order details with save feedback and audit events.
How to test
bun run check
bun run test
bun run build:web
Manual checks:
- Sign in as an employee, open an order, add a note, and verify it displays successfully.
- Refresh the page and confirm the note persists.
- Update the note and confirm an audit event appears.
- Confirm empty notes cannot be saved and notes are limited to 1,000 characters.
- Confirm customer users cannot update internal notes.
Screenshots or recordings
Attach a screenshot or recording of the Internal notes panel.
Risks / follow-ups
- Saving notes replaces the existing note instead of maintaining a threaded history.
- Simultaneous edits could overwrite another employee’s changes.
## PR checklist
- [ ] change is scoped to one ticket or one small reviewable concern
- [ ] acceptance criteria were checked
- [ ] code follows `CONTRIBUTING.md`
- [ ] no unrelated refactor is mixed in
- [ ] debug code and temporary logs are removed
- [ ] relevant automated checks were run locally
- [ ] changed behavior was manually tested when needed
- [ ] known risks or follow-ups are called out
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
Operations teammates can now add and update internal notes on an order. Notes persist as part of the order record, providing internal context for follow-up work.
What changed
How to test
bun run check
bun run test
bun run build:web
Manual checks:
Screenshots or recordings
Attach a screenshot or recording of the Internal notes panel.
Risks / follow-ups
PR checklist
CONTRIBUTING.mdView command line instructions
Checkout
From your project repository, check out a new branch and test the changes.