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 #3060] [Feature] Keyboard shortcut to only add single transaction #42895

New Issue
Closed
opened 2026-04-26 03:04:05 -05:00 by GiteaMirror · 7 comments
GiteaMirror commented 2026-04-26 03:04:05 -05:00
Owner
Copy Link

Originally created by @JukeboxRhino on GitHub (Jul 15, 2024).
Original GitHub issue: https://github.com/actualbudget/actual/issues/3060

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?

Currently, pressing Enter when finishing a new transaction adds your transaction, and then starts a new one. There is no way to only add a single transaction without remaining in the editing state for a new transaction besides entering your transaction and then clicking "Cancel".

Describe your ideal solution to this problem

I think that there should either be:

  1. A dedicated keyboard shortcut (Shift+Enter? Ctrl+Enter?) to only add a single transaction and finish editing.
  2. A new keyboard shortcut that maintains the current behavior and continues editing, and pressing Enter will only add one transaction and then finish.

Personally I think 2 is the better option based on the assumption that most people are only adding a single transaction at a time to an account, and that the more common use case should be the one with less friction.

Additionally, I feel like we should ask if adding a transaction by clicking the "Add" button should automatically start another transaction as well. I think the "Add" button should have the same functionality as pressing Enter, whichever way that goes.

Teaching and learning

The new keyboard shortcut could be included in the help modal which displays keyboard shortcuts implemented in #3033.

Originally created by @JukeboxRhino on GitHub (Jul 15, 2024). Original GitHub issue: https://github.com/actualbudget/actual/issues/3060 ### 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? Currently, pressing Enter when finishing a new transaction adds your transaction, and then starts a new one. There is no way to only add a single transaction without remaining in the editing state for a new transaction besides entering your transaction and then clicking "Cancel". ### Describe your ideal solution to this problem I think that there should either be: 1. A dedicated keyboard shortcut (Shift+Enter? Ctrl+Enter?) to only add a single transaction and finish editing. 2. A new keyboard shortcut that maintains the current behavior and continues editing, and pressing Enter will only add one transaction and then finish. Personally I think 2 is the better option based on the assumption that most people are only adding a single transaction at a time to an account, and that the more common use case should be the one with less friction. Additionally, I feel like we should ask if adding a transaction by clicking the "Add" button should automatically start another transaction as well. I think the "Add" button should have the same functionality as pressing Enter, whichever way that goes. ### Teaching and learning The new keyboard shortcut could be included in the help modal which displays keyboard shortcuts implemented in #3033.
GiteaMirror added the feature label 2026-04-26 03:04:05 -05:00
GiteaMirror commented 2026-04-26 03:04:07 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jul 15, 2024):

✨ 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:2229401220 --> @github-actions[bot] commented on GitHub (Jul 15, 2024): :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-26 03:04:08 -05:00
Author
Owner
Copy Link

@psybers commented on GitHub (Jul 16, 2024):

Perhaps ctrl (cmd on mac) plus enter?

Less than ideal workaround, but for me I can hit ENTER then hit ESC two times and get it done.

<!-- gh-comment-id:2229683350 --> @psybers commented on GitHub (Jul 16, 2024): Perhaps ctrl (cmd on mac) plus enter? Less than ideal workaround, but for me I can hit ENTER then hit ESC two times and get it done.
GiteaMirror commented 2026-04-26 03:04:10 -05:00
Author
Owner
Copy Link

@psybers commented on GitHub (Jul 16, 2024):

As far as your '1 vs 2' argument, I honestly don't know the most common case. I think that if someone is using bank sync (for the account currently being viewed!) then option 2 would be more common. You rarely add things by hand. If someone is not using bank sync, they add everything and then option 1 might make more sense?

<!-- gh-comment-id:2229689272 --> @psybers commented on GitHub (Jul 16, 2024): As far as your '1 vs 2' argument, I honestly don't know the most common case. I think that if someone is using bank sync (for the account currently being viewed!) then option 2 would be more common. You rarely add things by hand. If someone is not using bank sync, they add everything and then option 1 might make more sense?
GiteaMirror commented 2026-04-26 03:04:11 -05:00
Author
Owner
Copy Link

@psybers commented on GitHub (Jul 16, 2024):

Dupe of #1310. Perhaps close the old one in favor of this one that has conversation in it?

<!-- gh-comment-id:2229692577 --> @psybers commented on GitHub (Jul 16, 2024): Dupe of #1310. Perhaps close the old one in favor of this one that has conversation in it?
GiteaMirror commented 2026-04-26 03:04:12 -05:00
Author
Owner
Copy Link

@JukeboxRhino commented on GitHub (Jul 16, 2024):

As far as your '1 vs 2' argument, I honestly don't know the most common case. I think that if someone is using bank sync (for the account currently being viewed!) then option 2 would be more common. You rarely add things by hand. If someone is not using bank sync, they add everything and then option 1 might make more sense?

Yeah, I can only say that personally I don't use bank sync but rather I'm entering transactions manually on my phone as I make them. If I'm entering a transaction on web, I'm usually entering one at a time. However, I'm not trying to optimize the app for just my use case here. I would like to know how other people use it. We can at least make adding just one transaction a little smoother

<!-- gh-comment-id:2229696307 --> @JukeboxRhino commented on GitHub (Jul 16, 2024): > As far as your '1 vs 2' argument, I honestly don't know the most common case. I think that if someone is using bank sync (for the account currently being viewed!) then option 2 would be more common. You rarely add things by hand. If someone is not using bank sync, they add everything and then option 1 might make more sense? Yeah, I can only say that personally I don't use bank sync but rather I'm entering transactions manually on my phone as I make them. If I'm entering a transaction on web, I'm usually entering one at a time. However, I'm not trying to optimize the app for just my use case here. I would like to know how other people use it. We can at least make adding just one transaction a little smoother
GiteaMirror commented 2026-04-26 03:04:13 -05:00
Author
Owner
Copy Link

@alex-t-grey commented on GitHub (Jul 16, 2024):

I use a combo of banc sync and manual entry, and most cases I'm entering one at a time. To be honest, I didn't even notice that YNAB uses the same behavior where Enter = Save and Add Another, and I think it's because their Add New Transaction will close/cancel automatically when you click elsewhere in the register, which was enough to reduce friction for me. In Actual, it stays open until I specifically click Cancel or switch to a different part of the budget.

They also have separate buttons for Save and Save and add another, which I think would be a good addition to the Actual UI regardless of which behavior is associated with Enter vs some other shortcut

As for specific shortcut proposals Shift + Enter feels intuitive to me for Add Another. It reminds me of many messaging/commenting interfaces where Enter will send and Shift + Enter will give you a line break to keep adding more text.

<!-- gh-comment-id:2230818714 --> @alex-t-grey commented on GitHub (Jul 16, 2024): I use a combo of banc sync and manual entry, and most cases I'm entering one at a time. To be honest, I didn't even notice that YNAB uses the same behavior where `Enter = Save and Add Another`, and I think it's because their `Add New Transaction` will close/cancel automatically when you click elsewhere in the register, which was enough to reduce friction for me. In Actual, it stays open until I specifically click `Cancel` or switch to a different part of the budget. They also have separate buttons for `Save` and `Save and add another`, which I think would be a good addition to the Actual UI regardless of which behavior is associated with `Enter` vs some other shortcut As for specific shortcut proposals `Shift + Enter` feels intuitive to me for `Add Another`. It reminds me of many messaging/commenting interfaces where `Enter` will send and `Shift + Enter` will give you a line break to keep adding more text.
GiteaMirror commented 2026-04-26 03:04:15 -05:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Oct 18, 2024):

duplicate of #1310

<!-- gh-comment-id:2423004117 --> @youngcw commented on GitHub (Oct 18, 2024): duplicate of #1310
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#42895
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?