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 #1767] [Bug]: Category search no longer finds groups #7602

New Issue
Closed
opened 2026-04-10 17:29:56 -05:00 by GiteaMirror · 5 comments
GiteaMirror commented 2026-04-10 17:29:56 -05:00
Owner
Copy Link

Originally created by @andyvandesand on GitHub (Oct 7, 2023).
Original GitHub issue: https://github.com/actualbudget/actual/issues/1767

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

After updating to v23.10.0 I noticed when going through transactions and assigning categories that typing the name of a category group no longer brings up the categories within that group. This was very helpful - for example, I have a cateogry "Other" in a number of different category groups, and can now only type in "other" which will bring up the list of all "other"s that I have to select from, as opposed to typing e.g. "groceries" and having the right one close by. This made the process much quicker.

I'm almost certain this worked in the previous version!

What error did you receive?

No response

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Microsoft Edge

Operating System

Windows 11

Originally created by @andyvandesand on GitHub (Oct 7, 2023). Original GitHub issue: https://github.com/actualbudget/actual/issues/1767 ### Verified issue does not already exist? - [X] I have searched and found no existing issue ### What happened? After updating to v23.10.0 I noticed when going through transactions and assigning categories that typing the name of a category group no longer brings up the categories within that group. This was very helpful - for example, I have a cateogry "Other" in a number of different category groups, and can now only type in "other" which will bring up the list of all "other"s that I have to select from, as opposed to typing e.g. "groceries" and having the right one close by. This made the process much quicker. I'm almost certain this worked in the previous version! ### What error did you receive? _No response_ ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Microsoft Edge ### Operating System Windows 11
GiteaMirror added the bug label 2026-04-10 17:29:56 -05:00
GiteaMirror commented 2026-04-10 17:29:57 -05:00
Author
Owner
Copy Link

@Kidglove57 commented on GitHub (Oct 7, 2023):

@andyvandesand

I believe this is the result of a different request to have the category groups excluded. See #1681

I guess we all have different use cases. I am easy whether groups are included or excluded in the search to allocate a category to a transaction.

<!-- gh-comment-id:1751633502 --> @Kidglove57 commented on GitHub (Oct 7, 2023): @andyvandesand I believe this is the result of a different request to have the category groups excluded. See #1681 I guess we all have different use cases. I am easy whether groups are included or excluded in the search to allocate a category to a transaction.
GiteaMirror commented 2026-04-10 17:29:57 -05:00
Author
Owner
Copy Link

@andyvandesand commented on GitHub (Oct 7, 2023):

Hmm, sorry not sure why this didn't come up in my search, I figured it must have been something like this.
How about making it a setting then?

<!-- gh-comment-id:1751636011 --> @andyvandesand commented on GitHub (Oct 7, 2023): Hmm, sorry not sure why this didn't come up in my search, I figured it must have been something like this. How about making it a setting then?
GiteaMirror commented 2026-04-10 17:29:57 -05:00
Author
Owner
Copy Link

@Kidglove57 commented on GitHub (Oct 7, 2023):

In any event, personally I feel overall it is best to include category groups in the search . It helps for orientation and to reassure that the right budget category has been selected for that transaction.

So personally my vote would be to revert the change or, as you say, make it optional although I have no idea how hard this would be to code.

<!-- gh-comment-id:1751637052 --> @Kidglove57 commented on GitHub (Oct 7, 2023): In any event, personally I feel overall it is best to **include** category groups in the search . It helps for orientation and to reassure that the right budget category has been selected for that transaction. So personally my vote would be to revert the change or, as you say, make it optional although I have no idea how hard this would be to code.
GiteaMirror commented 2026-04-10 17:29:58 -05:00
Author
Owner
Copy Link

@mgrixti commented on GitHub (Dec 7, 2023):

I would second reverting the change. I personally find it easier to remember 10-15ish groups rather than 50+ categories. It seems to me that having strategically named groups to limit search results overlap is more reasonable than limiting all the other users from searching by the parent group.

<!-- gh-comment-id:1845870752 --> @mgrixti commented on GitHub (Dec 7, 2023): I would second reverting the change. I personally find it easier to remember 10-15ish groups rather than 50+ categories. It seems to me that having strategically named groups to limit search results overlap is more reasonable than limiting all the other users from searching by the parent group.
GiteaMirror commented 2026-04-10 17:29:58 -05:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Feb 4, 2024):

Closing this in favor of feature request #2324

<!-- gh-comment-id:1925931503 --> @youngcw commented on GitHub (Feb 4, 2024): Closing this in favor of feature request #2324
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
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#7602
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?