Team-segregated backlog health and per-person hygiene. Configure Neutara Ticketing in Settings to enable the Live sections, and/or upload an Excel export for the file-backed tabs.
Score starts at 100 and is docked for stale tickets, missing priority/labels/components/due date, overdue tickets, tickets resolved without a proper "Closed" status, and closed tickets with no image attachment on them.
| Assignee | Team | Touched | Open now | Stale | Missing details | Overdue | Closed (window) | Resolved w/o closure | Screenshot compliance | Hygiene score |
|---|---|---|---|---|---|---|---|---|---|---|
| — | ||||||||||
Every ticket reopened at least once within the date range above.
—
A ticket counts if it was created OR updated in the selected date range. One row per person. Breached splits into Retry (summary contains retry/conflict(s)/"not moving"/stuck/"not picking") and Non-retry.
A repository of Root Cause Analysis write-ups, organized by migration manager and then by project — static content, not pulled from Jira.
Credentials are stored server-side in config.json (never sent back to the browser in full, never logged). A full sync pulls the entire ticket history and takes several minutes — it runs automatically in the background (every few hours) and can also be triggered on demand below.
Expected columns: Issue Type, Key, Summary, Assignee, Reporter, Components, Combination, Priority, Status, Resolution, Created, Updated, Due date, First Response SLA Breach, Resolution SLA Breach. Key prefix decides the team: L2B/L3B → Customer Engineering, IN → Infra, QA → QA. CFITS rows are kept but not attributed to a team (see README — ENT vs SMB can't be split from this sheet alone).
Team tickets by individual can use Live Neutara Ticketing or your Uploaded Excel. Pick using the toggle shown at the top of that tab.