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

[GH-ISSUE #2324] [Feature] Search by Category Including Subcategory #50031

New Issue
Closed
opened 2026-04-30 12:45:52 -05:00 by GiteaMirror · 5 comments
GiteaMirror commented 2026-04-30 12:45:52 -05:00
Owner
Copy Link

Originally created by @Crazypkr1099 on GitHub (Feb 3, 2024).
Original GitHub issue: https://github.com/actualbudget/actual/issues/2324

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?

When searching for a category, it doesn't show the category, causing people who don't remember their subcategory name to have to go back to the report page, remember the category name and then search by it.

This was a feature that was removed to improve the search function for people who memorized their subcategories.

As a person who has tons of subcategories, this makes it extremely difficult, and I would like this reverted.

In addition, this did not follow the proper protocol of being put to a vote, but instead hidden inside a bug feature report.

Describe your ideal solution to this problem

Either revert the change or add a setting option to toggle this on/off, as shown in #1767

Teaching and learning

No response

Originally created by @Crazypkr1099 on GitHub (Feb 3, 2024). Original GitHub issue: https://github.com/actualbudget/actual/issues/2324 ### 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? When searching for a category, it doesn't show the category, causing people who don't remember their subcategory name to have to go back to the report page, remember the category name and then search by it. This was a feature that was removed to improve the search function for people who memorized their subcategories. As a person who has tons of subcategories, this makes it extremely difficult, and I would like this reverted. In addition, this did not follow the proper protocol of being put to a vote, but instead hidden inside a bug feature report. ### Describe your ideal solution to this problem Either revert the change or add a setting option to toggle this on/off, as shown in #1767 ### Teaching and learning _No response_
GiteaMirror added the feature label 2026-04-30 12:45:52 -05:00
GiteaMirror commented 2026-04-30 12:45:55 -05:00
Author
Owner
Copy Link

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

<!-- gh-comment-id:1925369581 --> @github-actions[bot] commented on GitHub (Feb 3, 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 -->
GiteaMirror commented 2026-04-30 12:45:56 -05:00
Author
Owner
Copy Link

@MatissJanis commented on GitHub (Feb 3, 2024):

Related: https://github.com/actualbudget/actual/issues/1615

<!-- gh-comment-id:1925370127 --> @MatissJanis commented on GitHub (Feb 3, 2024): Related: https://github.com/actualbudget/actual/issues/1615
GiteaMirror commented 2026-04-30 12:45:56 -05:00
Author
Owner
Copy Link

@yoyotogblo commented on GitHub (Feb 3, 2024):

I vote for reverting the change so we can search category groups. When you have the same category in many groups, it's much faster to search by category group. Also, in cases where one can't remember the specific category, it helps to search by the group. Can't think of any real strong reason for the original change to have been made. An extra click isn't too big a deal.

<!-- gh-comment-id:1925370159 --> @yoyotogblo commented on GitHub (Feb 3, 2024): I vote for reverting the change so we can search category groups. When you have the same category in many groups, it's much faster to search by category group. Also, in cases where one can't remember the specific category, it helps to search by the group. Can't think of any real strong reason for the original change to have been made. An extra click isn't too big a deal.
GiteaMirror commented 2026-04-30 12:45:57 -05:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Jun 18, 2024):

@Crazypkr1099 Is this good to close as a completed feature?

<!-- gh-comment-id:2176921494 --> @youngcw commented on GitHub (Jun 18, 2024): @Crazypkr1099 Is this good to close as a completed feature?
GiteaMirror commented 2026-04-30 12:45:57 -05:00
Author
Owner
Copy Link

@Crazypkr1099 commented on GitHub (Jun 18, 2024):

@Crazypkr1099 Is this good to close as a completed feature?

Yessir thanks!

<!-- gh-comment-id:2176942228 --> @Crazypkr1099 commented on GitHub (Jun 18, 2024): > @Crazypkr1099 Is this good to close as a completed feature? Yessir thanks!
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
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#50031
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?