github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-07 20:38:54 -05:00
Code Issues 1.6k Packages Projects Releases 55 Wiki Activity

[GH-ISSUE #2458] Customisable "Look Ahead" for Scheduled Transactions #26778

New Issue
Closed
opened 2026-04-18 03:06:26 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-18 03:06:26 -05:00
Owner
Copy Link

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?

  • I have searched and found no existing issue

💻

  • Would you like to implement this feature?

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.

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? - [X] I have searched and found no existing issue ### 💻 - [ ] Would you like to implement this feature? ### 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.
GiteaMirror added the feature label 2026-04-18 03:06:26 -05:00
GiteaMirror commented 2026-04-18 03:06:28 -05:00
Author
Owner
Copy Link

@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 👍!

<!-- gh-comment-id:1991724750 --> @github-actions[bot] commented on GitHub (Mar 12, 2024): :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 -->
GiteaMirror commented 2026-04-18 03:06:28 -05:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Mar 12, 2024):

duplicate of #1890

<!-- gh-comment-id:1991768339 --> @youngcw commented on GitHub (Mar 12, 2024): duplicate of #1890
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
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#26778
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?