mirror of
https://github.com/actualbudget/actual.git
synced 2026-03-09 19:52:56 -05:00
[Bug]: Schedule upcoming length in years doesn't calculate properly #2729
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/actual#2729
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 @youngcw on GitHub (Dec 17, 2025).
Verified issue does not already exist?
What happened?
When setting the schedule upcoming length to use years, there is an off by 1 error.
For example. If you set the upcoming length to be 1 year, you only see maybe one instance of the schedule, where if you set upcoming to be for 2 years, you see the upcoming year of schedules.
How can we reproduce the issue?
Make a schedule that repeats
Set the upcoming length to be 1 year, see that you don't get a whole year of schedules listed in the account page.
Set the upcoming length to be 2 years, see that 1 year of upcoming schedules show in the account page.
Where are you hosting Actual?
None
What browsers are you seeing the problem on?
No response
Operating System
None
@youngcw commented on GitHub (Dec 17, 2025):
Using months seems to work fine, so maybe the years option could simply multiply by 12 and then use the months code.
@Ani07-05 commented on GitHub (Dec 17, 2025):
could I take this up ?
@youngcw commented on GitHub (Dec 17, 2025):
@Ani07-05 Feel free
@Ani07-05 commented on GitHub (Dec 17, 2025):
@youngcw raised a PR please check it out , thank you !