github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-03-10 04:02:38 -05:00
Code Issues 250 Packages Projects Releases 53 Wiki Activity

[Feature] Customizable Date range for scheduled transactions in bank account #722

New Issue
Closed
opened 2026-02-28 19:15:02 -06:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-02-28 19:15:02 -06:00
Owner
Copy Link

Originally created by @msmith8fti on GitHub (Nov 9, 2023).

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?

In an account, it does currently show a number of scheduled transactions - I believe up to one week. It would be beneficial to be able to customize the number of upcoming transactions to see in the account register.

Describe your ideal solution to this problem

  • A custom setting to configure the date range
  • The ability to directly add a transaction from the schedule to the account; with the schedule showing the transaction as pending

Teaching and learning

No response

Originally created by @msmith8fti on GitHub (Nov 9, 2023). ### Verified feature request does not already exist? - [X] I have searched and found no existing issue ### 💻 - [X] Would you like to implement this feature? ### Pitch: what problem are you trying to solve? In an account, it does currently show a number of scheduled transactions - I believe up to one week. It would be beneficial to be able to customize the number of upcoming transactions to see in the account register. ### Describe your ideal solution to this problem - A custom setting to configure the date range - The ability to directly add a transaction from the schedule to the account; with the schedule showing the transaction as pending ### Teaching and learning _No response_
GiteaMirror added the feature label 2026-02-28 19:15:02 -06:00
GiteaMirror commented 2026-02-28 19:15:03 -06:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Nov 9, 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 👍!

@github-actions[bot] commented on GitHub (Nov 9, 2023): :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-02-28 19:15:03 -06:00
Author
Owner
Copy Link

@ricketyboo commented on GitHub (Nov 30, 2023):

This is something I've been keen to have as well and I did start digging into the logic for this a couple months ago but had to pause it.

I am probably going to try to pick this feature up over the holiday period when I have free time.

Once I have a better understanding of the schedule and transaction table and life cycle I'll post a proposed set of mockups for new experience and get some feedback.

One thing that needs to be addressed is that currently schedules that repeat within that preview period don't show the repeats. This would be critical for my own needs for extending the scheduled duration. I will add a separate issue for that and link these two together as that one probably needs to be fixed before this one.

From memory, (correct me if I'm wrong anyone who knows better) when I looked into this before the scheduled transactions are actually stored as records in the DB themselves, and not calculated in real time (sensible for performance) but this means if the schedule preview window is configurable we would have to generate or delete new schedule entries every time the configured value changes. This would probably preclude things like being able to change the duration from the accounts view, as nice as that would be.

@ricketyboo commented on GitHub (Nov 30, 2023): This is something I've been keen to have as well and I did start digging into the logic for this a couple months ago but had to pause it. I am probably going to try to pick this feature up over the holiday period when I have free time. Once I have a better understanding of the schedule and transaction table and life cycle I'll post a proposed set of mockups for new experience and get some feedback. One thing that needs to be addressed is that currently schedules that repeat within that preview period don't show the repeats. This would be critical for my own needs for extending the scheduled duration. I will add a separate issue for that and link these two together as that one probably needs to be fixed before this one. From memory, (correct me if I'm wrong anyone who knows better) when I looked into this before the scheduled transactions are actually stored as records in the DB themselves, and not calculated in real time (sensible for performance) but this means if the schedule preview window is configurable we would have to generate or delete new schedule entries every time the configured value changes. This would probably preclude things like being able to change the duration from the accounts view, as nice as that would be.
GiteaMirror commented 2026-02-28 19:15:04 -06:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Oct 11, 2024):

Added by #3310 Closing

@youngcw commented on GitHub (Oct 11, 2024): Added by #3310 Closing
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#722
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?