github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-07-16 07:04:23 -05:00
Code Issues 3.0k Packages Projects Releases 58 Wiki Activity

[GH-ISSUE #6250] [Feature] Quarterly grouping in reports #28447

New Issue
Closed
opened 2026-04-18 05:12:26 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-18 05:12:26 -05:00
Owner
Copy Link

Originally created by @dvanic on GitHub (Nov 26, 2025).
Original GitHub issue: https://github.com/actualbudget/actual/issues/6250

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?

Hi! I was updating my reports as part of my end of year review and realised that there is no way to group between annually and monthly - where quarterly would make sense.

This would be useful because some things (council rates in Australia, school fees etc) are charged quarterly, but also - when a monthly table widget is not expanded in dashboard view you don't get to see all of the months - but changing that to annual spending reduces the granularity of being able to look at suspiciously high periods to understand overspending:

Image

Overall, though, quarterly views in reports would help the dashboard be more useful per se, without needing to always expand monthly aggregated views to explore the numbers.

Describe your ideal solution to this problem

Add the ability to group quarterly (i.e. 3 months).

How would this work? If it's a dynamic view, then (let's say it's November), we group (Nov-Oct-Sep) - (Aug-Jul-Jun)-(May-Apr-Mar)-(Jan-Feb-Dec).

Teaching and learning

Adding it as an option when discussing reporting in the docs - although I think it's a relatively expected feature based on other apps.

Originally created by @dvanic on GitHub (Nov 26, 2025). Original GitHub issue: https://github.com/actualbudget/actual/issues/6250 ### 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? Hi! I was updating my reports as part of my end of year review and realised that there is no way to group between annually and monthly - where quarterly would make sense. This would be useful because some things (council rates in Australia, school fees etc) are charged quarterly, but also - when a monthly table widget is not expanded in dashboard view you don't get to see all of the months - but changing that to annual spending reduces the granularity of being able to look at suspiciously high periods to understand overspending: <img width="546" height="149" alt="Image" src="https://github.com/user-attachments/assets/827b9bb9-8756-4944-9ec5-3a86baf82d37" /> Overall, though, quarterly views in reports would help the dashboard be more useful per se, without needing to always expand monthly aggregated views to explore the numbers. ### Describe your ideal solution to this problem Add the ability to group quarterly (i.e. 3 months). How would this work? If it's a dynamic view, then (let's say it's November), we group (Nov-Oct-Sep) - (Aug-Jul-Jun)-(May-Apr-Mar)-(Jan-Feb-Dec). ### Teaching and learning Adding it as an option when discussing reporting in the docs - although I think it's a relatively expected feature based on other apps.
GiteaMirror added the needs votesfeature labels 2026-04-18 05:12:26 -05:00
GiteaMirror commented 2026-04-18 05:12:28 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Nov 26, 2025):

✨ 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:3578517144 --> @github-actions[bot] commented on GitHub (Nov 26, 2025): :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.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
AI generated
API
bank sync
budgeting
bug
can’t replicate
dependencies
docker
documentation
electron
experimental feature
feature
feedback
goal templates
good first issue
help wanted
importers
maintenance
needs info
needs testing
needs triage
needs votes
openid
payees
pull-request
Mirrored from GitHub Pull Request
 regression
reports
responsive
rules
schedules
server
✨ merged
split transactions
tech debt
tech-support
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label feature needs votes
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#28447
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?