[GH-ISSUE #7636] [Feature] A toggle-able 'Date Filter' for report pages #52260

Closed
opened 2026-04-30 20:31:06 -05:00 by GiteaMirror · 1 comment
Owner

Originally created by @HStep20 on GitHub (Apr 27, 2026).
Original GitHub issue: https://github.com/actualbudget/actual/issues/7636

Verified feature request does not already exist?

  • I have searched and found no existing issue

💻

  • Would you like to implement this feature?

Pitch: what problem are you trying to solve?

My biggest problem right now is that I have a hard time with custom reports in viewing actual numbers for different periods of time. The summary card is amazing for pulling quick insights out of a budget, but the downside is that you need multiple of them to visualize any number over time.

For example, I have 4 Report Tabs right now that are pretty close direct copies of each other, but for different time periods: Last Year, YTD, Last Month, MTD.

These let me benchmark my spending across different periods of time and get easily viewable numbers surfaced to the top. Of course, the problem is that for each custom report, I need 4 copies of the report (each with different timeframes) and that adds a ton of bloat to the 'add a widget' menu. On top of that, it makes maintaining/adding any new report a pain since I have to do it once for each 4 applicable tabs

Describe your ideal solution to this problem

What I'd love to be able to do is have a special type of Report Page which has a date selector exposed at the top of the page. From there, you could select any date range available to all the reports on the page (Last Year, YtD, MtD, Last Month, 1 year, 6 months, 1 month, etc) and it would apply that date filter to every single report on the page.

No more fiddling with dates for 30+ report widgets when you want to make something new, but instead you just go to your "Budget Breakdown" report page, and select the date range you want to see insights for.

Of course, its easier said than done because I can already think of a few edge cases:

  • Should Formula Cards not be effected? Because formula cards can have multiple different date ranges associated, it seems like these should not be included. But what if the two queries in a formula card share a date, then should it be effected by this?
  • Should each report have a new setting inside of it instead to 'follow report page-level dates' so that you can include some and exclude others? This would let you hide the setting on reports that might not be compatible with this 'parent date' line of thinking

Teaching and learning

No response

Originally created by @HStep20 on GitHub (Apr 27, 2026). Original GitHub issue: https://github.com/actualbudget/actual/issues/7636 ### Verified feature request does not already exist? - [x] I have searched and found no existing issue ### 💻 - [ ] Would you like to implement this feature? ### Pitch: what problem are you trying to solve? My biggest problem right now is that I have a hard time with custom reports in viewing actual numbers for different periods of time. The summary card is amazing for pulling quick insights out of a budget, but the downside is that you need multiple of them to visualize any number over time. For example, I have 4 Report Tabs right now that are pretty close direct copies of each other, but for different time periods: **Last Year, YTD, Last Month, MTD.** These let me benchmark my spending across different periods of time and get easily viewable numbers surfaced to the top. Of course, the problem is that for each custom report, I need 4 copies of the report (each with different timeframes) and that adds a ton of bloat to the 'add a widget' menu. On top of that, it makes maintaining/adding any new report a pain since I have to do it once for each 4 applicable tabs ### Describe your ideal solution to this problem What I'd love to be able to do is have a special type of Report Page which has a date selector exposed at the top of the page. From there, you could select any date range available to all the reports on the page (Last Year, YtD, MtD, Last Month, 1 year, 6 months, 1 month, etc) and it would apply that date filter to every single report on the page. No more fiddling with dates for 30+ report widgets when you want to make something new, but instead you just go to your "Budget Breakdown" report page, and select the date range you want to see insights for. Of course, its easier said than done because I can already think of a few edge cases: - Should Formula Cards not be effected? Because formula cards can have multiple different date ranges associated, it seems like these should not be included. But what if the two queries in a formula card share a date, then should it be effected by this? - Should each report have a new setting inside of it instead to 'follow report page-level dates' so that you can include some and exclude others? This would let you hide the setting on reports that might not be compatible with this 'parent date' line of thinking ### Teaching and learning _No response_
GiteaMirror added the needs votesfeature labels 2026-04-30 20:31:10 -05:00
Author
Owner

@github-actions[bot] commented on GitHub (Apr 27, 2026):

Thanks for sharing your idea!

This repository uses a voting-based system for feature requests. While enhancement issues are automatically closed, we still welcome feature requests! The voting system helps us gauge community interest in potential features. We also encourage community contributions for any feature requests marked as needing votes (just post a comment first so we can help guide you toward a successful contribution).

The enhancement backlog can be found here: https://github.com/actualbudget/actual/issues?q=label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc+

Don't forget to upvote the top comment with 👍!

<!-- gh-comment-id:4329029289 --> @github-actions[bot] commented on GitHub (Apr 27, 2026): :sparkles: Thanks for sharing your idea! :sparkles: This repository uses a voting-based system for feature requests. While enhancement issues are automatically closed, we still welcome feature requests! The voting system helps us gauge community interest in potential features. We also encourage community contributions for any feature requests marked as needing votes (just post a comment first so we can help guide you toward a successful contribution). The enhancement backlog can be found here: https://github.com/actualbudget/actual/issues?q=label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc+ Don't forget to upvote the top comment with 👍! <!-- feature-auto-close-comment -->
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#52260