mirror of
https://github.com/actualbudget/actual.git
synced 2026-03-22 08:52:49 -05:00
[Feature] Dim future transactions in register. #2587
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/actual#2587
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 @Crosis47 on GitHub (Nov 3, 2025).
Verified feature request does not already exist?
💻
Pitch: what problem are you trying to solve?
When looking at the account register, it is not easy to tell at a glance where the boundary between future transactions and past transactions is. As an example, in Quicken, future transactions have a darker background on their rows in the register. This allows a user to very easily find the boundary to get a glance at upcoming vs already past transactions.
Describe your ideal solution to this problem
The best way to solve this would just be to add a function that just dims the background color on a row that is dated (possibly font as well) after today's date.
Teaching and learning
Ideally it would just always be active as it does not harm the functionality of the software and just gives users an easier way to see one more statistic at a glance. This also helps users find their current year-to-date running balance if that is needing to be known.
@github-actions[bot] commented on GitHub (Nov 3, 2025):
✨ Thanks for sharing your idea! ✨
This repository uses a voting-based system for feature requests. While enhancement issues are automatically closed, we still welcome feature requests! The voting system helps us gauge community interest in potential features. We also encourage community contributions for any feature requests marked as needing votes (just post a comment first so we can help guide you toward 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 👍!
@matt-fidd commented on GitHub (Nov 3, 2025):
This should already be the case if you use schedules for future transactions
@Crosis47 commented on GitHub (Nov 3, 2025):
While that is true, I end up with quite a few transactions that I enter a few days in advance that are easier to just enter rather than go through the process of creating a schedule. If future transactions were to automatically convert to scheduled transactions, that would probably help the situation. I saw this functionality talked about in another request so that may be coming.
I am still learning the ins and outs of Actual as I just installed it in my Docker instance a few days ago. So I am not sure if this is correct, but if a transaction is scheduled, it is uncategorized and must be categorized after it has been fully entered in the register, correct?
@matt-fidd commented on GitHub (Nov 4, 2025):
I've been meaning to take a look at this for a while, but you've prompted me to finally get it done. Can you try out the preview build and try adding a future dated transaction, and let me know what you think? https://deploy-preview-6065.demo.actualbudget.org/
You can add a category but you've got to add it to the actions section in the schedule rule like this
@Crosis47 commented on GitHub (Nov 4, 2025):
I just tested it and I commend you on the work here. I really like this functionality, especially that it sets the rule for the notes and category as entered. Just to be sure, I also tested it's use when entering a transfer and that appears to be working perfectly as well.
Just curious as I think it would be a very simple change and also applies to schedules, what do you think of the idea I had in issue #6063 and how difficult would it be to implement? I used Quicken for years prior to Actual and it is a feature I always wished it had as well.
@Crosis47 commented on GitHub (Nov 4, 2025):
I did notice a bug while playing around with it that I don't think would be related to this code but seems like an oversight, If you choose "Post Transaction Today" on a schedule, it just posts a transaction from the schedule dated for today and links it but doesn't increment the schedule or mark it paid in any way. I figure this is because the logic is just looking for a transaction dated for the date the schedule is set for. I'm not sure how difficult that would be to fix or if it is something that is designed that way purposely but it definitely seems like marking paid should be the intended result of that menu choice.
@matt-fidd commented on GitHub (Nov 4, 2025):
Glad you like it, I was trying to make it as easy as possible, otherwise people just wouldn't use it.
Yep, youngcw found that too. It's the behaviour in-app at the moment and isn't actually related to my change, but it does make it more obvious. I'll try and fix it this cycle, I did take a look when I was implementing "post transaction today" and I noticed it, but we'll see if I can get it over the line