github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-06 07:01:45 -05:00
Code Issues 1.5k Packages Projects Releases 54 Wiki Activity

[Feature] Forecast based on schedule, user input, and current state #1990

New Issue
Closed
opened 2026-02-28 20:00:40 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-02-28 20:00:40 -06:00
Owner
Copy Link

Originally created by @babbaBlues on GitHub (Mar 29, 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?

It would be awesome to have a forecast based on the current state, and 'imaginary' future schedules
e.g. enter an imaginary recurring transaction of 50,00 and see how it will affect the account in the next weeks, months, years, considering the current scheduled transactions and their time ranges.

I had this done in a spreadsheet and used it to calculate how much I can afford to add to monthly payments while still keeping in range of a certain goal for the year/next years.

  1. User clicks forecast
  2. User has the option to add a single 'right now' transaction to be considered in the forecast
  3. User has the option to add a recurring transaction to be considered in the forecast
  4. User selects forecast range( (days, weeks, months, years))
  5. Actual displays forecast based on selection in 4. -> daily(in case of days), weekly (in case of weeks), monthly(in case of months), yearly(in case of years)
  • The forecast shows the amount of money in each/affected account per <selected period(days,weeks,months,years)>
  • No estimation based on behavior of previous time periods -> only strict consideration of the current state and applying schedules and 'imaginary' transactions entered by the user.

Describe your ideal solution to this problem

No response

Teaching and learning

No response

Originally created by @babbaBlues on GitHub (Mar 29, 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? It would be awesome to have a forecast based on the current state, and 'imaginary' future schedules e.g. enter an imaginary recurring transaction of 50,00 and see how it will affect the account in the next weeks, months, years, considering the current scheduled transactions and their time ranges. I had this done in a spreadsheet and used it to calculate how much I can afford to add to monthly payments while still keeping in range of a certain goal for the year/next years. 1. User clicks forecast 2. User has the option to add a single 'right now' transaction to be considered in the forecast 3. User has the option to add a recurring transaction to be considered in the forecast 4. User selects forecast range(<n> (days, weeks, months, years)) 5. Actual displays forecast based on selection in 4. -> daily(in case of days), weekly (in case of weeks), monthly(in case of months), yearly(in case of years) - The forecast shows the amount of money in each/affected account per <selected period(days,weeks,months,years)> - No estimation based on behavior of previous time periods -> only strict consideration of the current state and applying schedules and 'imaginary' transactions entered by the user. ### Describe your ideal solution to this problem _No response_ ### Teaching and learning _No response_
GiteaMirror added the needs votesfeature labels 2026-02-28 20:00:40 -06:00
GiteaMirror commented 2026-02-28 20:00:41 -06:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Mar 29, 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 (Mar 29, 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 -->
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
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#1990
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?