Skip to content

v0.7.6

Choose a tag to compare

@mpge mpge released this 22 Oct 20:35
· 52 commits to main since this release
2d06366

Added

  • The basic report sub-screens, at escalated-laravel's paths: Admin/Reports/AgentMetrics
    (admin/reports/agents/), Admin/Reports/SlaReport (admin/reports/sla/) and
    Admin/Reports/CsatReport (admin/reports/csat/), with the props its
    Admin\ReportController passes: per-agent tickets, resolved and average
    first response and resolution hours; SLA compliance overall and per active
    policy with the latest 100 breaches; and the CSAT average, response rate,
    per-agent ratings and daily averages. They read days (default 30).
  • tests/test_page_name_parity.py keeps a NOT_YET_RENDERED ledger of the
    shipped pages this package does not render yet.
  • The customer knowledge base pages, as escalated-laravel's
    Customer/KnowledgeBaseController: Customer/KnowledgeBase/Index at kb/
    (published articles, newest first, 15 a page, search and category
    filters, root categories with their published article counts) and
    Customer/KnowledgeBase/Article at kb/<slug>/ (counts the view, up to five
    related articles), with helpful / not helpful feedback posted to
    kb/<slug>/feedback/ (404 when feedback is off). The knowledge base answers
    404 when knowledge_base_enabled is off and 403 to visitors who are not
    signed in unless knowledge_base_public is on. Articles shown to readers
    leave out the author.
  • Admin/Reports/AgentDetail at admin/reports/agent/<id>/detail/
    (admin_reports_agent_detail), admins only, with the props the shared page
    declares: period_days, agent {id, name, email}, total_tickets,
    resolved_tickets, avg_frt, avg_resolution, csat_score (null without
    ratings), response_percentiles {p50..p99}, productivity (per day
    {label, value, values: [public replies, resolved]}), workload (tickets
    created per day), csat_breakdown (N stars counts), and prev_* for the
    same number of days before. It reads days (default 30).

Fixed

  • The reports overview and dashboard show figures. Admin/Reports was sent
    stats, by_department and csat.breakdown keyed 1..5, and
    Admin/Reports/Dashboard was sent ticket_volume and {status, count} /
    {priority, count} rows; the shared screens read none of those, so both
    rendered zeroes and empty charts. They now carry escalated-laravel's
    Admin\ReportController props and read days (default 30): the overview
    sends period_days, total_tickets, resolved_tickets,
    avg_first_response_hours, sla_breach_count, by_status / by_priority
    maps and csat {average, total, breakdown}; the dashboard sends
    period_days, volume, by_status, by_priority ({label, value} rows),
    avg_response_hours, avg_resolution_hours (from first_response_at and
    resolved_at), sla_compliance (from the breach flags), csat_average
    and agent_performance. ReportingService itself is unchanged.