CopilotKit / CopilotKit/outpost
Set escalation assignees — routing dead-ends at 'no team member found'
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 7
- Forks
- 3
- Avg merge
- 7d 16h
- Merged PRs (30d)
- 15
Description
Escalation routing runs, matches, and then dead-ends: the ticket is left unassigned with "no team member found — ticket left unassigned". No team members are configured as escalation targets.
Why it matters
Escalation is the safety net under the AI — the path a ticket takes when the bot cannot or should not answer. Right now that path terminates in an unassigned ticket that nobody is notified about, which is indistinguishable from the ticket having been dropped. It is a configuration gap rather than a code bug, which is part of why it is easy to miss.
Fix
Set escalation assignees per category/area, verify a test escalation reaches a real person, and decide what should happen when no assignee matches — a fallback assignee is better than silence.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the escalation-routing configuration for category/area assignees and trace how a test escalation handles the no-team-member case. Verify that a test escalation reaches a real person and document or implement the chosen fallback when no assignee matches.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100