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

[GH-ISSUE #1310] Add ability to manually enter single transaction #7430

New Issue
Closed
opened 2026-04-10 17:15:35 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-10 17:15:35 -05:00
Owner
Copy Link

Originally created by @deftly1970 on GitHub (Jul 7, 2023).
Original GitHub issue: https://github.com/actualbudget/actual/issues/1310

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 when entering transactions manually, after entering the details of the transaction, the user has the option to either hit the Enter key or to click the "Add" button. When either of these is done, the transaction is entered and new, blank transaction is opened.
If a user wishes to enter only a single transaction for the account they are currently in, the only way to do this is to hit enter or click add, and then hit the Escape key twice to close the blank transaction.
This is somewhat related to #1301 that points out how a transaction could be mistakenly entered in the wrong account because of the fact that the new open transaction persists while moving between account.

Describe your ideal solution to this problem

I propose that a new method be added to enable the entry of a single transaction by either hitting Shift+Enter or CMD+Enter. Another option would be to add another button in this area in addition to the "Add" button, similar to YNAB 4, which has a "Save and New" as well as a "Save and Close" button in the data entry area.

Teaching and learning

No response

Originally created by @deftly1970 on GitHub (Jul 7, 2023). Original GitHub issue: https://github.com/actualbudget/actual/issues/1310 ### 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? Currently when entering transactions manually, after entering the details of the transaction, the user has the option to either hit the Enter key or to click the "Add" button. When either of these is done, the transaction is entered and new, blank transaction is opened. If a user wishes to enter only a single transaction for the account they are currently in, the only way to do this is to hit enter or click add, and then hit the Escape key twice to close the blank transaction. This is somewhat related to #1301 that points out how a transaction could be mistakenly entered in the wrong account because of the fact that the new open transaction persists while moving between account. ### Describe your ideal solution to this problem I propose that a new method be added to enable the entry of a single transaction by either hitting Shift+Enter or CMD+Enter. Another option would be to add another button in this area in addition to the "Add" button, similar to YNAB 4, which has a "Save and New" as well as a "Save and Close" button in the data entry area. ### Teaching and learning _No response_
GiteaMirror added the needs votesfeature labels 2026-04-10 17:15:35 -05:00
GiteaMirror commented 2026-04-10 17:15:37 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jul 7, 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:1625904005 --> @github-actions[bot] commented on GitHub (Jul 7, 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-10 17:15:38 -05:00
Author
Owner
Copy Link

@shawalli commented on GitHub (Aug 15, 2024):

Alternatively, add another button that differentiates between "Add" and "Add and Start New Transaction" (this is how YNAB 4 did it).

<!-- gh-comment-id:2290130734 --> @shawalli commented on GitHub (Aug 15, 2024): Alternatively, add another button that differentiates between "Add" and "Add and Start New Transaction" (this is how YNAB 4 did it).
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#7430
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?