fix(admin): persist dashboard date range in the URL - #2922
Conversation
Keep the selected timeframe across reloads and tab switches via range/start/end query params. Co-authored-by: Cursor <cursoragent@cursor.com>
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 3 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (4)
Comment |
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_2eb6a181-13eb-4d4b-8865-6825761e4312) |
Merging this PR will not alter performance
Comparing Footnotes
|
|



Summary (AI generated)
range, plusstart/endfor custom)Motivation (AI generated)
Selecting a date range was lost on reload because it only lived in Pinia memory. Keeping it in the URL makes the current timeframe bookmarkable and stable across refreshes.
Business Impact (AI generated)
Faster admin workflows when reviewing users/orgs over a chosen window; shared links open on the same timeframe.
Test Plan (AI generated)
/admin/dashboard/users— URL gains?range=30day(or current default)?range=7dayrange=custom&start=...&end=...; reload restores itrangequery is preserved?range=14dayin a fresh session — page loads on 14 daysGenerated with AI
Made with Cursor
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.