github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-06 07:01:45 -05:00
Code Issues 1.5k Packages Projects Releases 54 Wiki Activity

[GH-ISSUE #1165] [Feature] Reorder transactions of the same date #49566

New Issue
Closed
opened 2026-04-30 11:07:23 -05:00 by GiteaMirror · 8 comments
GiteaMirror commented 2026-04-30 11:07:23 -05:00
Owner
Copy Link

Originally created by @joel-jeremy on GitHub (Jun 22, 2023).
Original GitHub issue: https://github.com/actualbudget/actual/issues/1165

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?

Sometimes you forget to enter a transaction for a specific date and when you do, the transaction goes in as the last transaction on that date. There is no easy way to insert the new transaction in the middle of the other transactions. As consequence of that, user would be seeing an inaccurate running balance.

Describe your ideal solution to this problem

As a user, I want to be able to reorder my transactions of the same date in the transactions table.
As a user, I should not be able be able to put a transaction with a later date before another transaction with an earlier date in the transactions table or vice versa.

Teaching and learning

No response

Originally created by @joel-jeremy on GitHub (Jun 22, 2023). Original GitHub issue: https://github.com/actualbudget/actual/issues/1165 ### 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? Sometimes you forget to enter a transaction for a specific date and when you do, the transaction goes in as the last transaction on that date. There is no easy way to insert the new transaction in the middle of the other transactions. As consequence of that, user would be seeing an inaccurate running balance. ### Describe your ideal solution to this problem As a user, I want to be able to reorder my transactions of the same date in the transactions table. As a user, I should not be able be able to put a transaction with a later date before another transaction with an earlier date in the transactions table or vice versa. ### Teaching and learning _No response_
GiteaMirror added the feature label 2026-04-30 11:07:23 -05:00
GiteaMirror commented 2026-04-30 11:07:25 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jun 22, 2023):

✨ Thanks for sharing your idea! ✨

This repository is now using lodash style issue management for enhancements. This means enhancement issues will now be closed instead of leaving them open. 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:1602977671 --> @github-actions[bot] commented on GitHub (Jun 22, 2023): :sparkles: Thanks for sharing your idea! :sparkles: This repository is now using lodash style issue management for enhancements. This means enhancement issues will now be closed instead of leaving them open. 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-30 11:07:27 -05:00
Author
Owner
Copy Link

@mcmikemn commented on GitHub (Mar 3, 2025):

One possible solution (that would work great for me!) is to use timestamps instead of dates. Actual could display only the date, but if it stores a timestamp then ca use the time of day to sort same-day transactions chronologically.

<!-- gh-comment-id:2694049426 --> @mcmikemn commented on GitHub (Mar 3, 2025): One possible solution (that would work great for me!) is to use timestamps instead of dates. Actual could _display_ only the date, but if it _stores_ a timestamp then ca use the time of day to sort same-day transactions chronologically.
GiteaMirror commented 2026-04-30 11:07:28 -05:00
Author
Owner
Copy Link

@Nyanino commented on GitHub (Sep 18, 2025):

One possible solution (that would work great for me!) is to use timestamps instead of dates. Actual could display only the date, but if it stores a timestamp then ca use the time of day to sort same-day transactions chronologically.

For transactions that don't have timestamps, an index can be assigned for each transaction for a given day. The transactions can then be dragged and dropped to arrange them appropriately, updating the index.

<!-- gh-comment-id:3308529649 --> @Nyanino commented on GitHub (Sep 18, 2025): > One possible solution (that would work great for me!) is to use timestamps instead of dates. Actual could _display_ only the date, but if it _stores_ a timestamp then ca use the time of day to sort same-day transactions chronologically. For transactions that don't have timestamps, an index can be assigned for each transaction for a given day. The transactions can then be dragged and dropped to arrange them appropriately, updating the index.
GiteaMirror commented 2026-04-30 11:07:29 -05:00
Author
Owner
Copy Link

@db-src commented on GitHub (Sep 26, 2025):

For the timestamp idea, see https://github.com/actualbudget/actual/issues/4289

<!-- gh-comment-id:3338168985 --> @db-src commented on GitHub (Sep 26, 2025): For the timestamp idea, see https://github.com/actualbudget/actual/issues/4289
GiteaMirror commented 2026-04-30 11:07:29 -05:00
Author
Owner
Copy Link

@HosseyNJF commented on GitHub (Jan 6, 2026):

Very ugly workaround if you really need it: When you change a transaction's date to a date in the future and then set it back to original, it will get moved to the top of the list on that day.

<!-- gh-comment-id:3714630000 --> @HosseyNJF commented on GitHub (Jan 6, 2026): Very ugly workaround if you really need it: When you change a transaction's date to a date in the future and then set it back to original, it will get moved to the top of the list on that day.
GiteaMirror commented 2026-04-30 11:07:29 -05:00
Author
Owner
Copy Link

@Nyanino commented on GitHub (Jan 6, 2026):

Very ugly workaround if you really need it: When you change a transaction's date to a date in the future and then set it back to original, it will get moved to the top of the list on that day.

Exactly what I’ve been doing, but as I’m sure you’ve noticed too, it takes so much effort.

<!-- gh-comment-id:3715023971 --> @Nyanino commented on GitHub (Jan 6, 2026): > Very ugly workaround if you really need it: When you change a transaction's date to a date in the future and then set it back to original, it will get moved to the top of the list on that day. Exactly what I’ve been doing, but as I’m sure you’ve noticed too, it takes so much effort.
GiteaMirror commented 2026-04-30 11:07:30 -05:00
Author
Owner
Copy Link

@icywhisker-official commented on GitHub (Feb 20, 2026):

Can I add that I would also prefer to be able to set a range for an expected scheduled transaction? I believe this improves the feature request and covers a broader approach. I find it nearly impossible to use bank sync and also set up schedules because of how I use the app. It's my fault, I should be useing the AI more but I wish to simply add a schedule and have tha pp auto detect the transaction, even if the transaction posts on a different or even eariler day. Allowing us to not only specify a unix time/time but also a range for a schedule would better suit my needs. I often have duplicate transactions. This wouldn't be much of an issue.... but if I delete the wrong transaction, When I sync again, the app recreates the transaction which may alarmingly drastically alter current or future projected balances.

<!-- gh-comment-id:3931746825 --> @icywhisker-official commented on GitHub (Feb 20, 2026): Can I add that I would also prefer to be able to set a range for an expected scheduled transaction? I believe this improves the feature request and covers a broader approach. I find it nearly impossible to use bank sync and also set up schedules because of how I use the app. It's my fault, I should be useing the AI more but I wish to simply add a schedule and have tha pp auto detect the transaction, even if the transaction posts on a different or even eariler day. Allowing us to not only specify a unix time/time but also a range for a schedule would better suit my needs. I often have duplicate transactions. This wouldn't be much of an issue.... but if I delete the wrong transaction, When I sync again, the app recreates the transaction which may alarmingly drastically alter current or future projected balances.
GiteaMirror commented 2026-04-30 11:07:31 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Mar 14, 2026):

🎉 This feature has been implemented in #6653 and will be released in the next version. Thanks for sharing your idea! 🎉

<!-- gh-comment-id:4060573119 --> @github-actions[bot] commented on GitHub (Mar 14, 2026): :tada: This feature has been implemented in #6653 and will be released in the next version. Thanks for sharing your idea! :tada: <!-- feature-implemented-comment -->
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#49566
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?