Refresh roadmap after Helpdesk validation

This commit is contained in:
Jason Thistlethwaite
2026-04-24 23:58:58 +00:00
parent fb6d0c2736
commit dde4dca8a2
4 changed files with 77 additions and 33 deletions
+2 -1
View File
@@ -37,10 +37,11 @@ while debugging:
The final output should include:
```text
[OK] redMCP issueWithHelpdesk returned ticket and message context
[OK] redMCP issueWithHelpdesk returned Helpdesk ticket context
[OK] redMCP default issue update did not send Helpdesk email
[OK] redMCP non-Helpdesk CRUD control passed
[OK] Mailpit received outbound Helpdesk/Redmine mail containing the reply token
[OK] redMCP issueWithHelpdesk returned post-reply journal message context
[OK] Closed smoke-test Helpdesk issue
Smoke test passed.
```
+29 -4
View File
@@ -25,11 +25,36 @@ environment. Before risky edits, archive the current plugin directories in
LAN Redmine copy.
- Short alias/usage routes were added to avoid noisy routing errors during
manual browser testing.
- Full end-to-end helpdesk outbox validation is still pending.
- Helpdesk mail import, Helpdesk metadata lookup, default non-email updates,
and explicit outbound Helpdesk replies are live-smoke-tested through redMCP.
- Helpdesk outbox/worker validation is still pending.
- Next meaningful milestone:
- Build the external worker/indexer that consumes `event_outbox_events`,
enriches via read-only MySQL joins, and emits deterministic ticket/message
documents for external indexing.
- Validate `redmine_outbox_worker.py` end to end against controlled Helpdesk
activity, document the derived JSONL shape, then choose the external index
target.
## 2026-04-24 - Helpdesk/redMCP Smoke Validation
- Touched areas:
- `redMCP`
- Helpdesk test tooling
- Purpose:
- Prove the LAN test instance can import a Helpdesk email, expose its
Helpdesk metadata through redMCP, update a non-Helpdesk control issue, send
an explicit Helpdesk reply, and verify outbound delivery through Mailpit.
- Make customer-visible Helpdesk email opt-in in redMCP.
- Behavior clarified:
- `RedMCP\RedmineClient::updateIssue()` uses the normal Redmine REST API and
does not send a Helpdesk email by default.
- `updateIssue(..., ['send_helpdesk_email' => true])` and
`sendHelpdeskIssueResponse()` deliberately use the Helpdesk email path.
- LAN test result:
- `./helpdesk_smoke_test.py` passed against `fud-helpdesk` and
`fud-nohelpdesk`.
- The smoke test verifies that a default issue update does not send Mailpit
mail, while an explicit Helpdesk response does.
- Latest documented passing run created and closed controlled Helpdesk issue
`#39871`.
## 2026-04-24 - POP3 Get Mail Compatibility Fix
+3 -2
View File
@@ -132,8 +132,9 @@ After the post-import checks pass, run the live Helpdesk/redMCP smoke test:
```
This imports a controlled Helpdesk email, verifies `issueWithHelpdesk()`, checks
non-Helpdesk CRUD, verifies outbound Mailpit delivery, and closes the created
test ticket. Details are in `docs/helpdesk_smoke_test.md`.
non-Helpdesk CRUD, confirms default updates do not send Helpdesk email, verifies
explicit outbound Mailpit delivery, and closes the created test ticket. Details
are in `docs/helpdesk_smoke_test.md`.
## 8. Re-Run The Read-Only Validator