github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-06 20:15:33 -05:00
Code Issues 1.5k Packages Projects Releases 55 Wiki Activity

[GH-ISSUE #5046] [Feature] Post transaction for scheduled / past date #27940

New Issue
Closed
opened 2026-04-18 04:33:22 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-18 04:33:22 -05:00
Owner
Copy Link

Originally created by @MvRens on GitHub (May 23, 2025).
Original GitHub issue: https://github.com/actualbudget/actual/issues/5046

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?

#4705 fixes an issue with when using "Post transaction today" on future schedules, which is nice. However, it also disrupted my workflow a bit for dates in the past. I don't budget daily, but maybe once a week. I have a fair amount of scheduled transactions which are accurate to the date most of the time, and when I get around to budgeting they show up as "Missed". I would use "Post transaction today" to confirm those transactions on the original scheduled date. With the bugfix it now moves those transactions to the current date, and I have to manually correct each one back.

Describe your ideal solution to this problem

Since the option now does what it says ("today") I hesitated to call this a bug. An easy change might be to not use a date which is in the future, but keep the original scheduled date when it is in the past. This keeps the functionality somewhat backwards compatible with either flow.

A better way might be to have a second option "Post on scheduled date"?

Teaching and learning

No response

Originally created by @MvRens on GitHub (May 23, 2025). Original GitHub issue: https://github.com/actualbudget/actual/issues/5046 ### 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? #4705 fixes an issue with when using "Post transaction today" on future schedules, which is nice. However, it also disrupted my workflow a bit for dates in the past. I don't budget daily, but maybe once a week. I have a fair amount of scheduled transactions which are accurate to the date most of the time, and when I get around to budgeting they show up as "Missed". I would use "Post transaction today" to confirm those transactions on the original scheduled date. With the bugfix it now moves those transactions to the current date, and I have to manually correct each one back. ### Describe your ideal solution to this problem Since the option now does what it says ("today") I hesitated to call this a bug. An easy change might be to not use a date which is in the future, but keep the original scheduled date when it is in the past. This keeps the functionality somewhat backwards compatible with either flow. A better way might be to have a second option "Post on scheduled date"? ### Teaching and learning _No response_
GiteaMirror added the feature label 2026-04-18 04:33:23 -05:00
GiteaMirror commented 2026-04-18 04:33:25 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (May 23, 2025):

✨ 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:2903445626 --> @github-actions[bot] commented on GitHub (May 23, 2025): :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 04:33:26 -05:00
Author
Owner
Copy Link

@MvRens commented on GitHub (Aug 5, 2025):

While I was making my own changes, it's been fixed in 25.8.0 by #5359 as well in a similar manner. thanks matt-fidd!

It looks like I can't remove the 'needs votes' label myself, but consider this feature request closed.

<!-- gh-comment-id:3153773110 --> @MvRens commented on GitHub (Aug 5, 2025): While I was making my own changes, it's been fixed in 25.8.0 by #5359 as well in a similar manner. thanks matt-fidd! It looks like I can't remove the 'needs votes' label myself, but consider this feature request closed.
GiteaMirror commented 2026-04-18 04:33:27 -05:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Aug 5, 2025):

This was added in v25.8

<!-- gh-comment-id:3156775286 --> @youngcw commented on GitHub (Aug 5, 2025): This was added in v25.8
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#27940
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?