mirror of
https://github.com/actualbudget/actual.git
synced 2026-07-15 22:54:03 -05:00
[GH-ISSUE #2458] Customisable "Look Ahead" for Scheduled Transactions #90614
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/actual#90614
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 @Phil89a on GitHub (Mar 12, 2024).
Original GitHub issue: https://github.com/actualbudget/actual/issues/2458
Verified feature request does not already exist?
💻
Pitch: what problem are you trying to solve?
Currently "upcoming" transactions are only auto-entered 7 days ahead. This means when looking ahead for the month, not all scheduled transactions are showing in the account and therefore your budget for that month is not complete. That is, it is missing regular income and spend. Result is you are not fully sure if you are over or under-spending for that month until the regular transaction come in (which could be at the end of the month)
Describe your ideal solution to this problem
Option 1 - Suggest a "number of days" field (default 7) is added to each schedule item, so the user can add the number of days ahead that should be used to test and see if the transaction should be auto-entered.
OR
Option 2 - A global setting added that allows this value to be set - and then applies to all schedule items.
Teaching and learning
Option 1 - No impact on user education. Default would be 7 days so no change unless the user changes the value in a schedule item. When users create or edit a schedule item, the option would be self explanatory.
Option 2 - No impact beyond explaining where the global setting is. Again default would be 7 days and so if not needed by the user no change required.
@github-actions[bot] commented on GitHub (Mar 12, 2024):
✨ 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 👍!
@youngcw commented on GitHub (Mar 12, 2024):
duplicate of #1890