mirror of
https://github.com/actualbudget/actual.git
synced 2026-07-11 11:59:55 -05:00
[Feature] Option to Require a Save Action After Edits (Toggle-able) #2735
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/actual#2735
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 @WEKarnesky on GitHub (Dec 21, 2025).
Verified feature request does not already exist?
💻
Pitch: what problem are you trying to solve?
The problem arises when manually adding or resolving transactions and adjusting their dates. In the current implementation, as soon as you click out of the date field, the changes are automatically saved. This can be problematic because if you are editing multiple fields or reviewing several transactions, the date change may jump around and the user is left searching for where it landed in the table. This behavior doesn’t provide an easy way to quickly undo or fix mistakes before finalizing the edit. Many users, especially those transitioning from YNAB, are used to a "save" step where all changes are made and then saved together, providing more control and flexibility when editing.
Describe your ideal solution to this problem
I would suggest making the current behavior a toggle-able option in the settings. This way, users who prefer the automatic save functionality can leave it as is, while users who want more control over their changes can enable a “manual save” mode. When this mode is activated, the date change (and any other field) would remain editable until the user explicitly clicks a “save” button or presses Enter. This would help users avoid unintended jumps in the transaction table and give them a chance to review their changes before finalizing them.
Teaching and learning
To make this feature discoverable, we could include it in the settings under a "Transaction Edit Options" section, with a short description of how it works. Documentation should explain the benefit of having the toggle for users coming from programs like YNAB, where the save step is standard. Additionally, a small tooltip or introductory tutorial could be shown when the feature is enabled for the first time, guiding users through how it works and how to toggle it off if they prefer the automatic saving behavior. The key to making it clear is to keep the language simple and not overload users with too many choices upfront.
@github-actions[bot] commented on GitHub (Dec 21, 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 👍!