[Feature] Add Running Average + Standard Deviation Curve to Custom Report Time Series #2062

Closed
opened 2026-02-28 20:02:20 -06:00 by GiteaMirror · 2 comments
Owner

Originally created by @MBueschelberger on GitHub (Apr 20, 2025).

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?

An option for an additional curve on top of the bar plot of the customized report displaying the running average (also called moving/rolling average) of the selected category would be a nice benefit.

Through this feature, a user can inspect how the average spending of the selected categories evolved through time, instead of having a static value for the overall selected time range.

Describe your ideal solution to this problem

The time window for this running average (e.g. the past 3 months before each regarded month in the time series of the report) should be customizable. Even if the time window is exceeding the date of the custom report (e.g. December 2024 is the first month of our report and we need to calculate the average of the 3 months before this date), the algorithm should automatically pick the relevant time units from outside the time range of the report, if available. If there is no data available in the time window before a certain date (e.g. we calculate the average with a time window of 3 months for December 2024 and the record only incorporates information until November 2024), the resulting value should be NaN.

Additionally, the option of including a shaded area with an upper and lower boundary determined by the standard deviation around the running average, would be very useful. See an example from plotly here: https://stackoverflow.com/questions/61494278/plotly-how-to-make-a-figure-with-multiple-lines-and-shaded-area-for-standard-de

Teaching and learning

No response

Originally created by @MBueschelberger on GitHub (Apr 20, 2025). ### 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? An option for an additional curve on top of the bar plot of the customized report displaying the running average (also called moving/rolling average) of the selected category would be a nice benefit. Through this feature, a user can inspect how the average spending of the selected categories evolved through time, instead of having a static value for the overall selected time range. ### Describe your ideal solution to this problem The time window for this running average (e.g. the past 3 months before each regarded month in the time series of the report) should be customizable. Even if the time window is exceeding the date of the custom report (e.g. December 2024 is the first month of our report and we need to calculate the average of the 3 months before this date), the algorithm should automatically pick the relevant time units from outside the time range of the report, if available. If there is no data available in the time window before a certain date (e.g. we calculate the average with a time window of 3 months for December 2024 and the record only incorporates information until November 2024), the resulting value should be `NaN`. Additionally, the option of including a shaded area with an upper and lower boundary determined by the standard deviation around the running average, would be very useful. See an example from plotly here: https://stackoverflow.com/questions/61494278/plotly-how-to-make-a-figure-with-multiple-lines-and-shaded-area-for-standard-de ### Teaching and learning _No response_
GiteaMirror added the needs votesfeature labels 2026-02-28 20:02:20 -06:00
Author
Owner

@github-actions[bot] commented on GitHub (Apr 20, 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 👍!

@github-actions[bot] commented on GitHub (Apr 20, 2025): :sparkles: Thanks for sharing your idea! :sparkles: 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 👍! <!-- feature-auto-close-comment -->
Author
Owner

@MBueschelberger commented on GitHub (Apr 20, 2025):

See an other example from plotly for the rolling average here:

https://stackoverflow.com/questions/59442383/moving-average-for-plotly

@MBueschelberger commented on GitHub (Apr 20, 2025): See an other example from plotly for the rolling average here: https://stackoverflow.com/questions/59442383/moving-average-for-plotly
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#2062