Enable Date range filter in dashboard and anti pattern pages

[kumaresan-subramani]

Problem

we cant see specified timeframe data propelry

Proposed Solution

Enable Date range filter in dashboard and anti pattern pages

Alternatives Considered

No response

[github-actions]

🎯 Triage report

This reads as a feature request for first-class date-range filtering on the Dashboard and Anti-Patterns pages rather than a bug report: the issue asks for a new control to make timeframe-specific analysis easier to inspect. The request is directionally clear, but it does not yet define the exact UX or how the new range filter should interact with existing page filters and summaries.

📊 Assessment

Dimension	Value	Reasoning
Type	Feature	No existing type was set, and the issue proposes new filtering capability rather than reporting a regression.
Labels	enhancement	The existing enhancement label matches the request; no additional label is strongly supported by the issue content.
Severity	Low	This is a usability/productivity improvement request with no evidence of broken core functionality or blocked workflows.
Coding agent	Needs more info	The target pages are clear, but implementation-ready details are missing: expected presets/custom range behavior, whether the filter is shared or per-page, and which cards/charts/tables it must affect.

💡 Notes and suggestions

Likely implementation surfaces:

• src/webview/page-dashboard.ts
• src/webview/page-antipatterns.ts

There is already a range-filter pattern in src/webview/page-patterns.ts (Last 7 days, Last 4 weeks, etc.) that may be reusable for UI consistency.

renderDashboard(container, currentFilter) and renderAntiPatterns(container, currentFilter) already accept a shared DateFilter, which suggests the main gap may be exposing and wiring page-level controls rather than introducing a brand-new filter model. In Anti-Patterns specifically, there is already at least one path that passes DateFilter into detail/explainer requests, so it is worth checking whether the missing behavior is mostly top-level page filtering and refresh logic.

Recommended clarification before implementation:

1. Should the date range be a shared global filter for both pages, or an independent control on each page?
2. Are quick presets enough, or is a custom from/to picker required?
3. On Dashboard, which data should respect the range: summary cards, daily activity, workspace breakdown, harness breakdown, anti-pattern preview, and code production?
4. On Anti-Patterns, should the range affect only charts/histograms, or also rule counts, scores, and occurrence details?

No high-confidence duplicate was found in the current issue search.

Generated by Agentic Triage for issue #174 · 104 AIC · ⌖ 19.7 AIC · ⊞ 22.4K · ◷

Add this agentic workflows to your repo

To install this agentic workflow, run

gh aw add githubnext/agentics/workflows/issue-triage.md@df35cf29fb856d1c3b8f023ed46d19126e7813bf