mirror of
https://github.com/actualbudget/actual.git
synced 2026-03-22 12:30:06 -05:00
[Feature] Show all scheduled repeats within the account scheduled transactions sections #775
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/actual#775
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 @ricketyboo on GitHub (Nov 30, 2023).
Verified feature request does not already exist?
💻
Pitch: what problem are you trying to solve?
If a scheduled transaction repeats within the period of time that is visible at the top of the account, only the first instance of the repeat is visible and factored into forecasts.
Example below of a transaction that repeats daily.
I want to work on https://github.com/actualbudget/actual/issues/1890 but the process of extending the visible range of scheduled transactions will make it more likely that this lack of visibility on repeats will start to cause concerns when users try to forecast.
For bonus points it'd be nice to be able to see the repeats in the schedules page as well, but I understand that would likely be a far more difficult solution and requires much more UX consideration. Perhaps a stretch goal or another feature request should this one be successful.
Describe your ideal solution to this problem
My understanding from when I looked into data structure a few months ago, and please correct me if I'm wrong, is that each scheduled entry is created as a real record in the DB and must therefore be generated / regenerated as schedule information changes.
Given my ultimate intent is to extend the time scale of shown scheduled transactions, I would expect that we need to update this generation logic to work based on the period of time we want to preview transactions, and generate all the scheduled entries that fall within that period of time. For the short term this can be a constant on par with current forecasting, but will be made dynamic later as part of 1890.
I suspect this may run into difficulties if the scheduler has no ability to look ahead without a previous entry being converted into a real transaction, but given the schedule editor itself has the repeat schedule listed, I am hopeful it will be possible to read this repeat schedule, and just call a generate method for every instance within the configured forecast range.
Teaching and learning
As described in the proposed solution, users shouldn't need to have anything explained and it should wind up more intuitive than what is currently in place. They will gain more information from their forecast, but as nothing in this work is configurable or opt-in
There should be minimal documentation change required. Perhaps some extra info in https://actualbudget.org/docs/budgeting/schedules or adding a new page explaining forecasts under https://actualbudget.org/docs/accounts/ as we don't seem to have documentation anywhere for the scheduled list at the top of the account, Perhaps I've overlooked it?
@github-actions[bot] commented on GitHub (Nov 30, 2023):
✨ 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 👍!
@matt-fidd commented on GitHub (Jan 29, 2025):
This has been implemented in https://github.com/actualbudget/actual/pull/4166