github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-03-09 11:42:54 -05:00
Code Issues 250 Packages Projects Releases 53 Wiki Activity

[Bug]: Mobile transaction entry 'remembers' last category on 2nd entry #1070

New Issue
Closed
opened 2026-02-28 19:30:39 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-02-28 19:30:39 -06:00
Owner
Copy Link

Originally created by @shall0pass on GitHub (May 3, 2024).

Verified issue does not already exist?

  • I have searched and found no existing issue
  • I will be providing steps how to reproduce the bug (in most cases this will also mean uploading a demo budget file)

What happened?

When manually entering a transaction on the mobile pages, on the first transaction entry the payee and category are blank and need to be filled. This is what I expect. If you then add a second transaction, the category field remains filled. I expect this to remain blank.

Why it matters:
I have rules set up to populate the category based on the payee. If the category is prefilled, my rules will not apply.

The mobile entry did not used to prefill the category, so this feels like a regression to me.

Where are you hosting Actual?

NAS

What browsers are you seeing the problem on?

Chrome

Operating System

Mobile Device

Originally created by @shall0pass on GitHub (May 3, 2024). ### Verified issue does not already exist? - [X] I have searched and found no existing issue - [X] I will be providing steps how to reproduce the bug (in most cases this will also mean uploading a demo budget file) ### What happened? When manually entering a transaction on the mobile pages, on the first transaction entry the payee and category are blank and need to be filled. This is what I expect. If you then add a second transaction, the category field remains filled. I expect this to remain blank. Why it matters: I have rules set up to populate the category based on the payee. If the category is prefilled, my rules will not apply. The mobile entry did not used to prefill the category, so this feels like a regression to me. ### Where are you hosting Actual? NAS ### What browsers are you seeing the problem on? Chrome ### Operating System Mobile Device
GiteaMirror added the regressionuser interfacegood first issuebugresponsive labels 2026-02-28 19:30:39 -06:00
GiteaMirror commented 2026-02-28 19:30:39 -06:00
Author
Owner
Copy Link

@tasawar-hussain commented on GitHub (May 5, 2024):

I would like to work on it

@tasawar-hussain commented on GitHub (May 5, 2024): I would like to work on it
GiteaMirror commented 2026-02-28 19:30:40 -06:00
Author
Owner
Copy Link

@brasilikum commented on GitHub (May 5, 2024):

Even if it's a transfer, the category of the last transfer is shown

@brasilikum commented on GitHub (May 5, 2024): Even if it's a transfer, the category of the last transfer is shown
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 bug good first issue regression responsive user interface
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#1070
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?