mirror of
https://github.com/actualbudget/actual.git
synced 2026-03-10 04:02:38 -05:00
[Feature] Add time span configuration to Spending Analysis report #1759
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/actual#1759
Reference in New Issue
Block a user
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?
Originally created by @kcollett on GitHub (Jan 10, 2025).
Verified feature request does not already exist?
💻
Pitch: what problem are you trying to solve?
The Spending Analysis report allows one to compare the current month spending to "Average". Looking at past activity, it looks like (I might be wrong) that this equates to comparing the current month spending to the previous three months of spending.
There two scenarios that come to mind that suggest the enhancements I'm proposing. The first is where you are making semi-annual payments that are substantial. For example, if you are making semi-annual payments for car insurance, then a three-month average will be misleading in that may be too high (if it captures the car insurance payment) or too low (if the car insurance payment falls outside of the three-month window). In this scenario, a 6-month window would be better.
The second scenario is where you are making irregularly-spaced payments over the course of a year. The example that comes to mind is estimated tax payments, which are due in April, June, September, and January. In this example, both a 3-month window and a 6-month window would lead to misleading averages; a 12-month window would avoid this problem.
Describe your ideal solution to this problem
I propose adding a configuration option to the Spending Analysis report where the user can specify how many months are used to compute the average that is used. Probably the most straightforward way is to have a radio button array corresponding to 3, 6, and 12 months.
Teaching and learning
In terms of discoverability,, I can't think of anything other than presenting something like the radio button array I propose for the solution. I suppose the documentation could mention the scenarios I described, but it probably makes sense to make them more relatable and less US-centric if possible. (Most people don't pay estimated taxes.)
@github-actions[bot] commented on GitHub (Jan 10, 2025):
✨ Thanks for sharing your idea! ✨
This repository uses lodash style issue management for enhancements. That means enhancement issues are automatically closed. This doesn’t mean we don’t accept feature requests, though! We will consider implementing ones that receive many upvotes, and we welcome contributions for any feature requests marked as needing votes (just post a comment first so we can help you make 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 👍!
@maciejmatczak commented on GitHub (Aug 4, 2025):
I would love to have the spending analysis with chosen range and static target.
I would help greatly in yearly budgeting. I forecast my yearly income, so it's linear and static. What I track is based on a query. Something like that:
@maciejmatczak commented on GitHub (Oct 17, 2025):
A real life example how this could look like (Plotly Dash +
actualpy):