feat(support): dashboard backend (statistics, escalation alerts, clerk mapping)#3942
Open
joshuakrueger-dfx wants to merge 1 commit into
Open
Conversation
joshuakrueger-dfx
requested review from
TaprootFreak and
davidleomay
as code owners
3 tasks
joshuakrueger-dfx
force-pushed
the
feat/support-dashboard-backend
branch
4 times, most recently
from
f3c59b5 to
043dce7
Compare
…k mapping)
- add GET support/issue/statistics?days=N with role-scoped, period-based aggregates (total, avg messages/ticket, tickets/day, day/month trend, avg resolution time per type)
- notify a Telegram group when a ticket escalates (customer waiting beyond the SLA) and for each new limit increase request; auto-bind + per-cycle de-duplication; chat id + state via SettingService; token from SUPPORT_TELEGRAM_BOT_TOKEN
- resolve the logged-in agent's clerk via GET support/issue/clerk, backed by the registered supportClerkAccounts setting ([{ account, name }])
joshuakrueger-dfx
force-pushed
the
feat/support-dashboard-backend
branch
from
043dce7 to
a768c04
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Support dashboard — backend
Adds the backend for the new support dashboard overview: ticket statistics, Telegram escalation alerts, and account→clerk resolution.
What's included
GET support/issue/statistics?days=N: role-scoped, period-based aggregates (total, avg messages/ticket, tickets/day, and a day- or month-bucketed trend depending on the period). MSSQL-side aggregation, no row dump.Config.support.escalation.slaHours= 24h). Auto-binds to the group it was invited to, de-duplicates per waiting cycle, and posts a clickable link to the ticket. Bot token fromSUPPORT_TELEGRAM_BOT_TOKEN; chat id + notified state viaSettingService(no schema change).GET support/issue/clerkreturns the clerk mapped to the logged-in account via the new registeredsupportClerkAccountssetting ([{ account, name }]). Replaces client-side identity.Setup (settings / ops)
SUPPORT_TELEGRAM_BOT_TOKEN.supportClerks(names for the assign dropdown):["Jana","Vesa","Cyrill","Josh"]supportClerkAccounts(account→name for "my tickets"):[{ "account": <JanaId>, "name": "Jana" }, { "account": <VesaId>, "name": "Vesa" }, { "account": <CyrillId>, "name": "Cyrill" }, { "account": <JoshId>, "name": "Josh" }]Release Checklist
Pre-Release
Post-Release
POST support/issue/escalation/telegram-test)