github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-11-12 03:42:19 -06:00
Code Issues 3.0k Packages Projects Releases 58 Wiki Activity

[GH-ISSUE #6062] [Feature] Dim future transactions in register. #92216

New Issue
Closed
opened 2026-05-26 02:58:07 -05:00 by GiteaMirror · 7 comments
GiteaMirror commented 2026-05-26 02:58:07 -05:00
Owner
Copy Link
Copy Source

Originally created by @Crosis47 on GitHub (Nov 3, 2025).
Original GitHub issue: https://github.com/actualbudget/actual/issues/6062

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?

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.

Originally created by @Crosis47 on GitHub (Nov 3, 2025). Original GitHub issue: https://github.com/actualbudget/actual/issues/6062 ### 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? 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.
GiteaMirror added the featureneeds votes labels 2026-05-26 02:58:08 -05:00
GiteaMirror commented 2026-05-26 02:58:13 -05:00
Author
Owner
Copy Link
Copy Source

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

<!-- gh-comment-id:3482284641 --> @github-actions[bot] commented on GitHub (Nov 3, 2025): :sparkles: Thanks for sharing your idea! :sparkles: 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 👍! <!-- feature-auto-close-comment -->
GiteaMirror commented 2026-05-26 02:58:15 -05:00
Author
Owner
Copy Link
Copy Source

@matt-fidd commented on GitHub (Nov 3, 2025):

This should already be the case if you use schedules for future transactions

Image
<!-- gh-comment-id:3482385978 --> @matt-fidd commented on GitHub (Nov 3, 2025): This should already be the case if you use schedules for future transactions <img width="1015" height="241" alt="Image" src="https://github.com/user-attachments/assets/47ab6466-75e5-4755-b1b1-fc96cea3bd62" />
GiteaMirror commented 2026-05-26 02:58:18 -05:00
Author
Owner
Copy Link
Copy Source

@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?

<!-- gh-comment-id:3482604852 --> @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?
GiteaMirror commented 2026-05-26 02:58:21 -05:00
Author
Owner
Copy Link
Copy Source

@matt-fidd commented on GitHub (Nov 4, 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'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/

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?

You can add a category but you've got to add it to the actions section in the schedule rule like this

Image
<!-- gh-comment-id:3483146360 --> @matt-fidd commented on GitHub (Nov 4, 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'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/ > 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? You can add a category but you've got to add it to the actions section in the schedule rule like this <img width="900" height="829" alt="Image" src="https://github.com/user-attachments/assets/c404d2b6-fe6e-41b9-9f54-9e418c8eccc7" />
GiteaMirror commented 2026-05-26 02:58:23 -05:00
Author
Owner
Copy Link
Copy Source

@Crosis47 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/

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.

<!-- gh-comment-id:3483549763 --> @Crosis47 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/ 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.
GiteaMirror commented 2026-05-26 02:58:24 -05:00
Author
Owner
Copy Link
Copy Source

@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.

<!-- gh-comment-id:3483599191 --> @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.
GiteaMirror commented 2026-05-26 02:58:27 -05:00
Author
Owner
Copy Link
Copy Source

@matt-fidd 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.

Glad you like it, I was trying to make it as easy as possible, otherwise people just wouldn't use it.

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.

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

<!-- gh-comment-id:3483632982 --> @matt-fidd 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. Glad you like it, I was trying to make it as easy as possible, otherwise people just wouldn't use it. > 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. 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
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
tech-support
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No labels feature needs votes
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
GiteaMirror ninjasurge (Kaehlen Rog)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#92216