Generated: 2026-03-02 11:39 EST | Data Source: JIRA | Tickets Analyzed: 1131
Sprint Range: Controls how many sprints are displayed across all charts. Select "Last 4", "Last 6", "Last 10", or "All Sprints" to adjust the time window.
Exclude Epic Points: When checked (default), Epic ticket story points are excluded from all point calculations. This prevents double-counting since Epic points often represent the sum of their child tickets. Uncheck this if your team tracks Epic points separately.
Exclude Epics from Counts: In the Ticket Counts tab, there's an additional checkbox to exclude Epic tickets from the ticket count visualizations. This is useful if you don't want Epic container tickets counted alongside individual work items.
Multi-Sprint Tickets: Tickets that appear in multiple sprints are only counted in their most recent sprint. Earlier sprints are excluded from rollups to avoid double-counting story points.
Dev vs QA Points: Points are split by the "Developer" and "QA Assignee" custom fields (not the standard Assignee field). A ticket's Dev Points go to the Developer, and QA Points go to the QA Assignee.
Latest Sprint Points: Shows the total points from the most recent sprint in the current filter range.
A ticket is considered completed for sprint metrics when its status is one of the following:
Note: Tickets transition from Verified → Done when the build is released to production, but for sprint metrics we count Verified as complete since the work is finished.
The metrics in this dashboard were generated from JIRA using the following JQL query:
project = LOPS AND "products[select list (multiple choices)]" IN (tfMRD, "Latitude (tfMRD)") AND "team[team]" = fee007ac-475e-494f-b3b7-91697cf32c09
You can run this query in JIRA to see the source tickets. Total tickets analyzed: 1131
All sprints in reverse chronological order (most recent first) with their start and end dates from JIRA. Use this as a reference when analyzing sprint data.
The following sprints are filtered from all metrics in this report:
| Sprint | Full Name | Start Date | End Date | Status |
|---|---|---|---|---|
| Sprint 63 | LOPS-tfMRD-63-20260223 | 2026-02-23 | 2026-03-09 | active |
| Sprint 62 | LOPS-tfMRD-62-20260209 | 2026-02-09 | 2026-02-23 | closed |
| Sprint 61 | LOPS-tfMRD-61-20260126 | 2026-01-26 | 2026-02-09 | closed |
| Sprint 60 | LOPS-tfMRD-60-20260112 | 2026-01-12 | 2026-01-26 | closed |
| Sprint 59 | LOPS-tfMRD-59-20251229 | 2025-12-29 | 2026-01-12 | closed |
| Sprint 58 | LOPS-tfMRD-58-20251215 | 2025-12-15 | 2025-12-29 | closed |
| Sprint 57 | LOPS-tfMRD-57-20251202 | 2025-12-01 | 2025-12-15 | closed |
| Sprint 56 | LOPS-tfMRD-56-20251117 | 2025-11-17 | 2025-12-02 | closed |
| Sprint 55 | LOPS-tfMRD-55-20251103 | 2025-11-03 | 2025-11-17 | closed |
| Sprint 54 | LOPS-tfMRD-54-20251020 | 2025-10-21 | 2025-11-03 | closed |
| Sprint 53 | LOPS-tfMRD-53-20251006 | 2025-10-06 | 2025-10-20 | closed |
| Sprint 52 | LOPS-tfMRD-52-20250922 | 2025-09-22 | 2025-10-06 | closed |
| Sprint 51 | LOPS-tfMRD-51-20250908 | 2025-09-08 | 2025-09-22 | closed |
| Sprint 50 | LOPS-tfMRD-50-20250825 | 2025-08-26 | 2025-09-06 | closed |
| Sprint 49 | LOPS-tfMRD-49-20250811 | 2025-08-12 | 2025-08-25 | closed |
| Sprint 48 | LOPS-tfMRD-48-20250728 | 2025-07-29 | 2025-08-11 | closed |
| Sprint 47 | LOPS-tfMRD-47-20250713 | 2025-07-15 | 2025-07-28 | closed |
| Sprint 46 | LOPS-tfMRD-46-20250630 | 2025-07-01 | 2025-07-14 | closed |
| Sprint 46 | LOPS Sprint 20250630 (46) | 2025-06-30 | 2025-07-14 | closed |
| Sprint 45 | LOPS Sprint 20250616 (45) | 2025-06-16 | 2025-06-30 | closed |
| Sprint 44 | LOPS Sprint 20250602 (44) | 2025-06-02 | 2025-06-16 | closed |
| Sprint 43 | LOPS Sprint 20250519 (43) | 2025-05-19 | 2025-06-02 | closed |
| Sprint 42 | LOPS Sprint 20250505 (42) | 2025-05-05 | 2025-05-19 | closed |
| Sprint 41 | LOPS Sprint 20250421 (41) | 2025-04-08 | 2025-05-05 | closed |
| Sprint 40 | LOPS Sprint 20250407 (40) | 2025-04-07 | 2025-04-19 | closed |
| Sprint 39 | LOPS Sprint 20250324 (39) | 2025-03-24 | 2025-04-07 | closed |
| Sprint 38 | LOPS Sprint 20250310 (38) | 2025-03-10 | 2025-03-24 | closed |
| Sprint 37 | LOPS Sprint 20250224 (37) | 2025-02-24 | 2025-03-07 | closed |
| Sprint 36 | LOPS Sprint 20250210 (36) | 2025-02-10 | 2025-02-21 | closed |
| Sprint 35 | LOPS Sprint 20250127 (35) | 2025-01-27 | 2025-02-07 | closed |
| Sprint 34 | LOPS Sprint 20250113 (34) | 2025-01-13 | 2025-01-25 | closed |
Total: 31 sprints shown
Pivot tables showing story points per person for each sprint. Rows are team members, columns are sprints. Cell color intensity indicates relative contribution. Use horizontal scroll if needed to see all sprints. Tables update when you change the sprint filter.
Number of tickets assigned to each team member per sprint, by role. Tables update when you change the sprint filter.
Tracks when Bug, Defect, and Sub-defect tickets were created (not when worked on). Useful for identifying quality trends and potential problem areas.
Analysis of tickets and story points by fix version. Tables show ticket types, point distribution, and sprint relationships.
Count of tickets in each fix version, broken down by ticket type.
Combined story points (Dev + QA) per fix version, broken down by ticket type.
Story points split by Dev and QA for each fix version.
Which sprints contributed work to each fix version. Uses most recent sprint for tickets spanning multiple sprints.
Shows how sprint scope changes after planning. Committed = tickets planned at sprint start. Added = tickets added mid-sprint (scope creep). Removed = tickets pulled out mid-sprint. The Scope Creep % line shows additions as a percentage of the original commitment.
Same analysis by story points to see effort impact. Toggle between Dev, QA, and Combined points to identify where scope creep comes from.
Shows what happened to work at sprint end. Completed = tickets marked Done/Closed/Verified. Not Completed (Rollover) = tickets still in sprint but not Done - these typically roll to next sprint. The Rollover Rate % line shows the percentage of sprint work that didn't finish.
Note: This visual tracks tickets that remain in the sprint when it ends. Tickets that are proactively moved out of the sprint before it closes (e.g., when the team identifies work won't be completed) are not captured here. Those removals appear in the "Sprint Scope Analysis (Ticket Counts)" visual above as "Removed Mid-Sprint". To get the full picture of work rolling from sprint to sprint, review both visuals together.