mirror of
https://github.com/actualbudget/actual.git
synced 2026-03-10 20:23:07 -05:00
[Feature] Filtering payees that have no rules #896
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/actual#896
Reference in New Issue
Block a user
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?
Originally created by @psybers on GitHub (Jan 27, 2024).
Verified feature request does not already exist?
💻
Pitch: what problem are you trying to solve?
Especially for new users that have imported a lot of past history, it takes quite awhile to build up a good set of rules for categorizing payees. As you add more and more rules, when you have hundreds of existing payees, it can be difficult to see what payees still need a rule added.
Describe your ideal solution to this problem
You can currently filter payees by typing in a string. I propose another way to filter: by those payees with or without rules. Then you can filter down to just your payees that have no rules yet and focus on adding rules for those.
This could be done via the UI (a button, checkbox, etc.) or by adding a filter string such as "has:rule". The second approach could be combined with the existing filter, so you could search for things like "has:rule amaz" to get all payees that match "amaz" that also have a rule. And then there would be need for negating it somehow, such as "not has:rule". This syntax is inspired by the search capabilities of GMail.
Or you can combine the two approaches: have the filter implemented via the search string, but then have a button (or two) that automatically populates the search field with "not has:rule" when clicked.
Teaching and learning
If it is a UI element, it probably is easily discoverable. If it is a search string, you will need to update the documentation to document the query syntax. You might want to provide a hint under the filter box that they can search for "not has:rule" etc. If you use the combined approach, it probably self-documents.
@github-actions[bot] commented on GitHub (Jan 27, 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 👍!