[Feature] Recurring Issue Detection #60

New Issue

2026-02-10T15:59:43Z

chihlasm commented

2026-02-10 15:59:43 +00:00

(Migrated from github.com)

Summary

When starting a session and entering a client name, show previous sessions for that client in that tree. If the same resolution keeps being reached, prompt for root cause action.

Why

Turns ResolutionFlow from reactive (fix the ticket) to proactive (fix the root cause). For MSP managers, recurring issues per client = business intelligence for infrastructure upgrade proposals.

UI

At session start: "3 previous sessions for Warner Robins in this tree (last: Jan 28)" + link to view
At resolution (if recurring): "This is the 3rd time this issue was resolved the same way for this client. Consider documenting a permanent fix or escalating to address root cause."

Implementation Notes

Query: sessions grouped by client_name + tree_id, count + last date
Display at session start (inline banner, not blocking)
Recurrence prompt: compare resolution node_id across sessions for same client+tree
No schema changes needed — queries existing sessions table
Optional: normalize client names (fuzzy match or future client_id foreign key)

Acceptance Criteria

Previous session count shown when client name matches existing sessions
Link to view past sessions for this client+tree combo
Recurrence warning when same resolution reached 3+ times
Non-blocking — informational only, doesn't prevent session start

Sources

docs/plans/2026-02-04-feature-ideas-brainstorm.md — Idea 8: Recurring Issue Detection
.claude/docs/ai/resolutionflow/10x/session-1.md — Massive #3 (Client Intelligence)

Priority

Do Next — leverages existing data, high value

## Summary When starting a session and entering a client name, show previous sessions for that client in that tree. If the same resolution keeps being reached, prompt for root cause action. ## Why Turns ResolutionFlow from reactive (fix the ticket) to proactive (fix the root cause). For MSP managers, recurring issues per client = business intelligence for infrastructure upgrade proposals. ## UI - At session start: "3 previous sessions for Warner Robins in this tree (last: Jan 28)" + link to view - At resolution (if recurring): "This is the 3rd time this issue was resolved the same way for this client. Consider documenting a permanent fix or escalating to address root cause." ## Implementation Notes - Query: sessions grouped by `client_name` + `tree_id`, count + last date - Display at session start (inline banner, not blocking) - Recurrence prompt: compare resolution `node_id` across sessions for same client+tree - No schema changes needed — queries existing sessions table - Optional: normalize client names (fuzzy match or future `client_id` foreign key) ## Acceptance Criteria - [ ] Previous session count shown when client name matches existing sessions - [ ] Link to view past sessions for this client+tree combo - [ ] Recurrence warning when same resolution reached 3+ times - [ ] Non-blocking — informational only, doesn't prevent session start ## Sources - `docs/plans/2026-02-04-feature-ideas-brainstorm.md` — Idea 8: Recurring Issue Detection - `.claude/docs/ai/resolutionflow/10x/session-1.md` — Massive #3 (Client Intelligence) ## Priority **Do Next** — leverages existing data, high value

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: chihlasm/resolutionflow#60