Date Ranges & Scoping
Choose the time window the CFD covers. The right date range depends on whether you are monitoring ongoing flow or analyzing a specific sprint or release.
Date Range Modes
| Mode | Description | Best For |
|---|---|---|
| Rolling days | Last N calendar days ending today | Ongoing Kanban monitoring |
| Custom date range | Specific from-date to to-date | Point-in-time analysis or reporting periods |
| Dates of a sprint | Scoped to sprint start and end dates | Sprint health and retrospectives |
| Project release dates | Scoped to a fix version's start/end dates | Release tracking and delivery analysis |
Rolling Days Options
Choose from: 7 days · 14 days · 30 days · 60 days · 90 days · 180 days
Use 7–14 days for active sprint monitoring. Use 30–90 days for Kanban flow trends and release tracking.
Sprint Scoping
- Set Date Range to Dates of a sprint
- Select a sprint from the dropdown
Latest Sprint Auto
Instead of selecting a specific sprint, choose "Latest sprint (auto)". The CFD automatically uses whichever sprint is currently active - no manual update needed when a new sprint starts.
Tip: Use "Latest sprint auto" on any permanent team dashboard so the CFD always shows the current sprint without anyone needing to reconfigure it.
Release / Version Scoping
- Set Date Range to Project release dates
- Select a fix version from the project's version list
- The chart spans from the version's start date to its release date
This is ideal for release health dashboards - the chart automatically scopes to your release window.
Interval Granularity
Control how many data points appear on the X-axis:
| Interval | Best For |
|---|---|
| 1 day | Short sprints, detailed monitoring |
| 1 week | Multi-week releases, quarterly views |
| 2 weeks | Longer release cycles |
| 1 month | Year-level or roadmap views |
Wider intervals produce smoother charts - useful when daily variation creates visual noise.