github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-07-16 07:04:23 -05:00
Code Issues 3.0k Packages Projects Releases 58 Wiki Activity

[GH-ISSUE #4982] [Feature]: Cannot clear category filled by rule while entering transaction #79556

New Issue
Closed
opened 2026-05-19 02:31:16 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-05-19 02:31:16 -05:00
Owner
Copy Link

Originally created by @keysmashes on GitHub (May 12, 2025).
Original GitHub issue: https://github.com/actualbudget/actual/issues/4982

Verified feature request does not already exist?

  • I have searched and found no existing issue

Pitch: what problem are you trying to solve?

While filling out a transaction, if the category is filled automatically by a rule (e.g. based on payee), it's not possible to clear that category without clicking "Add" and then editing the newly-added transaction.

Describe your ideal solution to this problem

If the category is cleared after a rule is applied, the category should not be immediately automatically filled by that rule again.

If the transaction is edited to match another rule, the category could potentially be automatically filled again.

Teaching and learning

I think manually clearing the category field is pretty intuitive, so I'm not sure that any documentation is needed.

Originally created by @keysmashes on GitHub (May 12, 2025). Original GitHub issue: https://github.com/actualbudget/actual/issues/4982 ### Verified feature request does not already exist? - [x] I have searched and found no existing issue ### Pitch: what problem are you trying to solve? While filling out a transaction, if the category is filled automatically by a rule (e.g. based on payee), it's not possible to clear that category without clicking "Add" and then editing the newly-added transaction. ### Describe your ideal solution to this problem If the category is cleared after a rule is applied, the category should not be immediately automatically filled by that rule again. If the transaction is edited to match another rule, the category could potentially be automatically filled again. ### Teaching and learning I think manually clearing the category field is pretty intuitive, so I'm not sure that any documentation is needed.
GiteaMirror added the featureneeds votes labels 2026-05-19 02:31:17 -05:00
GiteaMirror commented 2026-05-19 02:31:21 -05:00
Author
Owner
Copy Link

@youngcw commented on GitHub (May 12, 2025):

I think the answer is to remove the rule and disable category learning for that payee. That way Actual wont auto fill the category

<!-- gh-comment-id:2873901230 --> @youngcw commented on GitHub (May 12, 2025): I think the answer is to remove the rule and disable category learning for that payee. That way Actual wont auto fill the category
GiteaMirror commented 2026-05-19 02:31:21 -05:00
Author
Owner
Copy Link

@keysmashes commented on GitHub (May 12, 2025):

The rule is often useful, though. It's only in a minority of cases that it's wrong – but in those cases I often want a bit longer to think before I decide which category to pick, so I'd like to add the transaction with an empty category and be reminded to come back later by the big red "uncategorized transactions" warning.

<!-- gh-comment-id:2873910076 --> @keysmashes commented on GitHub (May 12, 2025): The rule is often useful, though. It's only in a minority of cases that it's wrong – but in those cases I often want a bit longer to think before I decide which category to pick, so I'd like to add the transaction with an empty category and be reminded to come back later by the big red "uncategorized transactions" warning.
GiteaMirror commented 2026-05-19 02:31:22 -05:00
Author
Owner
Copy Link

@youngcw commented on GitHub (May 12, 2025):

That would be a feature request then, to allow bypassing the rule.

<!-- gh-comment-id:2873917931 --> @youngcw commented on GitHub (May 12, 2025): That would be a feature request then, to allow bypassing the rule.
GiteaMirror commented 2026-05-19 02:31:23 -05:00
Author
Owner
Copy Link

@keysmashes commented on GitHub (May 12, 2025):

...sure. Do you want me to copy-paste the same text into a new issue template, or can this issue be repurposed?

<!-- gh-comment-id:2873965713 --> @keysmashes commented on GitHub (May 12, 2025): ...sure. Do you want me to copy-paste the same text into a new issue template, or can this issue be repurposed?
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
tech-support
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#79556
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?