mirror of
https://github.com/actualbudget/actual.git
synced 2026-07-16 07:04:23 -05:00
[GH-ISSUE #1675] [Feature] Allow manually entered future transactions to be included with the "upcoming" scheduled transactions for sort/display #98038
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/actual#98038
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 @Lunchtime0614 on GitHub (Sep 8, 2023).
Original GitHub issue: https://github.com/actualbudget/actual/issues/1675
Verified feature request does not already exist?
💻
Pitch: what problem are you trying to solve?
If you have a bunch of scheduled transactions they show at the top of the register as "upcoming" and date sort ignores these. However if you manually enter a future dated transaction that transaction is included in with everything else and is included with sort...so you can run into an issue with your running balance being incorrect.
Example:
You have a schedule for your paycheck ever 2 weeks - so it shows upcoming at the top and is excluded from sort. Say this is scheduled for the 15th of the month. But you also know you have a one-time bill or another payment that's due on the 16th....so you go ahead and enter it in your Actual Budget (and maybe you even schedule the bill pay from your bank). If you enter this future bill, it'll go in with your other transactions and be sorted by date accordingly. However it can make your running balance go negative because that "upcoming" paycheck scheduled transaction is at the top, not included in the transaction sorting.
Describe your ideal solution to this problem
Any future dated transaction be it manually entered or from a schedule should be considered "upcoming" like the schedule is today...and not included in the sorting of the transactions until that date comes.
Teaching and learning
None really needed - it's pretty apparent how it works today and if you keep all future transactions at the top together there will be no confusion.
@github-actions[bot] commented on GitHub (Sep 8, 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 👍!
@ricketyboo commented on GitHub (Nov 30, 2023):
Alternative suggestion for this feature:
Instead of using future dated transactions and sorting them into the scheduled section, overhaul the scheduled experience on account view to make it possible to add / edit schedule entries from there.
Extended Rationale and thinking:
It would probably be complicated from an implementation perspective, and confusing for the user experience, trying to make a transaction be sorted into the scheduled section. Especially if it sorts them into the middle of a series of un-editable scheduled transactions, as a normal transaction. The UX would need some careful consideration.
I'd suggest that the ability to have cleared / uncleared future dated transactions is a bit odd as a feature anywa, and would personally prefer to be able to edit the scheduled transactions more easily from inside the account view.
Perhaps people do have valid use cases for future dated transactions. Certainly the ability edit transactions from account view including fields you can't currently edit on a schedule without using rule sets instead of schedule level information. I'd suggest this is a short coming of schedules rather than an intended use of transactions however.
This might be better solved by allowing the "future transaction" to actually be created as a schedule from the account view, If we could somehow extract the schedule entry process into an inline edit like transactions, allowing the creation of a simple non-repeating schedule entry. If you need it to repeat or have more rules you could click through to the standard schedule editor?
@tavlima commented on GitHub (Feb 4, 2024):
Would something like https://github.com/actualbudget/actual/issues/2296 help?