github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-08 21:12:08 -05:00
Code Issues 1.6k Packages Projects Releases 55 Wiki Activity

[GH-ISSUE #6518] [Feature] Customize transaction entry behavior #51879

New Issue
Closed
opened 2026-04-30 19:40:11 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-30 19:40:11 -05:00
Owner
Copy Link

Originally created by @JarronKai on GitHub (Jan 1, 2026).
Original GitHub issue: https://github.com/actualbudget/actual/issues/6518

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?

Many folks enter one transaction at a time, and want to enter future dated transactions into the register directly. Both of these workflows require extra clicks, because Actual assumes that you always want to add another transaction (Add button by default opens another transaction entry, which you then have to cancel) and future dated transactions pop up a modal encouraging you to use schedules, which has to be clicked away.

Describe your ideal solution to this problem

There's good reasons to limit the number of buttons that exist, so let folks choose how the buttons behave in their settings. I think you would want two toggles related to the "Add" button on transactions ("Close on Add" / "Add another transaction on Add") and ("Post future dated transactions to the Register" / "Suggest Schedule for Future Dated Transactions").

Teaching and learning

In no particular order:

  • Highlight in the setup documentation
  • Place this section prominently in Settings, position 3 or 4?
  • Add this info to the model that pops up when creating a future dated transaction (you can go to Settings to change the behavior of the Add button)
Originally created by @JarronKai on GitHub (Jan 1, 2026). Original GitHub issue: https://github.com/actualbudget/actual/issues/6518 ### 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? Many folks enter one transaction at a time, and want to enter future dated transactions into the register directly. Both of these workflows require extra clicks, because Actual assumes that you always want to add another transaction (Add button by default opens another transaction entry, which you then have to cancel) and future dated transactions pop up a modal encouraging you to use schedules, which has to be clicked away. ### Describe your ideal solution to this problem There's good reasons to limit the number of buttons that exist, so let folks choose how the buttons behave in their settings. I think you would want two toggles related to the "Add" button on transactions ("Close on Add" / "Add another transaction on Add") and ("Post future dated transactions to the Register" / "Suggest Schedule for Future Dated Transactions"). ### Teaching and learning In no particular order: - Highlight in the setup documentation - Place this section prominently in Settings, position 3 or 4? - Add this info to the model that pops up when creating a future dated transaction (you can go to Settings to change the behavior of the Add button)
GiteaMirror added the needs votesfeature labels 2026-04-30 19:40:14 -05:00
GiteaMirror commented 2026-04-30 19:40:35 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jan 1, 2026):

✨ 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:3703124480 --> @github-actions[bot] commented on GitHub (Jan 1, 2026): :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-04-30 19:40:40 -05:00
Author
Owner
Copy Link

@Juulz commented on GitHub (Jan 1, 2026):

Note: ctrl/cmd + enter adds the transaction and closes the transaction form. 😀

<!-- gh-comment-id:3703793122 --> @Juulz commented on GitHub (Jan 1, 2026): Note: `ctrl/cmd + enter` adds the transaction and closes the transaction form. 😀
GiteaMirror commented 2026-04-30 19:40:43 -05:00
Author
Owner
Copy Link

@JarronKai commented on GitHub (Jan 1, 2026):

Note: ctrl/cmd + enter adds the transaction and closes the transaction form. 😀

I'm aware, I'd still prefer to have the option of changing the behavior of the button.

<!-- gh-comment-id:3704140562 --> @JarronKai commented on GitHub (Jan 1, 2026): > Note: `ctrl/cmd + enter` adds the transaction and closes the transaction form. 😀 I'm aware, I'd still prefer to have the option of changing the behavior of the button.
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 needs votes
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#51879
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?