[Feature] Mobile - Default account and "cleared" value when adding new transaction #1240

Closed
opened 2026-02-28 19:37:09 -06:00 by GiteaMirror · 3 comments
Owner

Originally created by @TailyFair on GitHub (Jul 16, 2024).

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?

On mobile I enter transactions on-the go as I do my payment/purchase and have little time to enter them. I most of the time use the same account when entering single transaction (via "+Transaction") and almost always transaction is already cleared.
So it becomes tedious to always do these steps and I would love to add transactions faster and more efficiently.

Describe your ideal solution to this problem

I would like to either:
a) Allow to customize defaults - default account and default "cleared" values
b) Always fill previous transaction values for account and "cleared" value

Teaching and learning

Maybe add settings modal in transactions page where you can set this up?

Originally created by @TailyFair on GitHub (Jul 16, 2024). ### 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? **On mobile** I enter transactions on-the go as I do my payment/purchase and have little time to enter them. I most of the time use the same account when entering single transaction (via "+Transaction") and almost always transaction is already cleared. So it becomes tedious to always do these steps and I would love to add transactions faster and more efficiently. ### Describe your ideal solution to this problem I would like to either: a) Allow to customize defaults - default account and default "cleared" values b) Always fill previous transaction values for account and "cleared" value ### Teaching and learning Maybe add settings modal in transactions page where you can set this up?
GiteaMirror added the needs votesfeature labels 2026-02-28 19:37:09 -06:00
Author
Owner

@github-actions[bot] commented on GitHub (Jul 16, 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 👍!

@github-actions[bot] commented on GitHub (Jul 16, 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 -->
Author
Owner

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

I believe a more accurate user story would be:

As a Mobile user, I want the New Transaction interface to automatically populate the "Account" field, so that I can reduce the number of button clicks and speed up transaction entry on the go.

The "Account" population rules could be one of the following options:

  1. A "favorite" or "default" account, chosen by the user
  2. The most frequently used account, as determined by transaction history
  3. The most recently used account, selection remembered from previously entered transaction (persistent across sessions)

I'm less on board with the "Cleared" behavior. It mainly seems useful for entering actual Cash transactions (e.g. you have an "account" tracking the cash in your wallet), where there is never a delay between when the transaction occurs and when it "clears". Perhaps "automatically clear transaction on entry" could be an Account setting? For example, this seems to be the only difference between Checking and Cash account types in YNAB

@atgrey24 commented on GitHub (Jul 16, 2024): I believe a more accurate user story would be: As a Mobile user, I want the New Transaction interface to automatically populate the "Account" field, so that I can reduce the number of button clicks and speed up transaction entry on the go. The "Account" population rules could be one of the following options: 1. A "favorite" or "default" account, chosen by the user 2. The most frequently used account, as determined by transaction history 3. The most recently used account, selection remembered from previously entered transaction (persistent across sessions) I'm less on board with the "Cleared" behavior. It mainly seems useful for entering actual Cash transactions (e.g. you have an "account" tracking the cash in your wallet), where there is never a delay between when the transaction occurs and when it "clears". Perhaps "automatically clear transaction on entry" could be an Account setting? For example, this seems to be the only difference between Checking and Cash account types in YNAB
Author
Owner

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

Seems like this issue can be solved by just using rules, as described here
https://actualbudget.org/docs/budgeting/rules/custom/#q-how-do-i-set-a-default-account-when-i-add-transactions

Just on mobile, it seems to be bugged setting Cleared value. Registered bug: https://github.com/actualbudget/actual/issues/3071

@TailyFair commented on GitHub (Jul 16, 2024): Seems like this issue can be solved by just using rules, as described here https://actualbudget.org/docs/budgeting/rules/custom/#q-how-do-i-set-a-default-account-when-i-add-transactions Just on mobile, it seems to be bugged setting Cleared value. Registered bug: https://github.com/actualbudget/actual/issues/3071
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#1240