Needs your attention
Monitor
What happened today
| Priority | Task | Stage | Assigned | Age | Created | Target End Date |
|---|
| Bug | Severity | Assignee | Responsible | Status | Reported | Target Date | Solved Date |
|---|
By project
| Project | Tested | Passed first time | Rework rate | Avg QA time |
|---|
| Title | Priority | Kind | Status | Date | Target Date |
|---|
What the team shipped
By employee
| Employee | Assigned tasks | Currently working on | Completed | Reworked |
|---|
Timeline by project
Bugs
Performance Snapshot
A data-based ranking, not a judgment call — built only from ticket data: completed work weighted by priority, resolved bugs weighted by severity (a bonus on top, since fixing a real reported problem counts for more than routine work of the same priority), and a penalty for tickets QA had to send back more than once. It doesn't see work that never became a ticket — mentoring, meetings, support — and a score built from only a handful of tickets in a short period is far less meaningful than one built from many, so read the "This Period" ranking below with that in mind.
This Period
All Time
Export PDF opens your browser's print dialog — choose "Save as PDF" as the destination, and turn on "Background graphics" (under More settings) for the full-color timeline bars.
Jira Connection
Status mapping
Every Jira status found in your projects, mapped to how this dashboard buckets work. Adjust and hit Save above.
| Jira status | Dashboard stage | Blocked? |
|---|
Notion Connection
Your team logs Bugs and Suggestions/Feedbacks in Notion; this pulls them in and links each one to its Jira ticket (matched from the "Related Tickets" link) once your dev team creates one — status, start date, and target fix date then always come live from that ticket. Add more than one source below if bugs/suggestions are tracked in more than one Notion database (e.g. a separate tracker per team) — each syncs independently.