[GH-ISSUE #2525] [Feature] More flexible filtering for Payee rules, like "starts with" and regex #42674

Closed
opened 2026-04-26 02:44:05 -05:00 by GiteaMirror · 7 comments
Owner

Originally created by @mattalxndr on GitHub (Mar 30, 2024).
Original GitHub issue: https://github.com/actualbudget/actual/issues/2525

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?

Screenshot_2024-03-30_03-07

As you can see in the screenshot, I have a ton of entries like PAYEE-NAME PAYEE-TXN-ID like "AIRBNB 934274932". I would like to define "If payee starts with AIRBNB , then ..." but it's not possible.

Describe your ideal solution to this problem

Being able to use regular expressions or glob expressions like "starts with" and "contains" would allow for much more flexibility when defining a rule.

Teaching and learning

No response

Originally created by @mattalxndr on GitHub (Mar 30, 2024). Original GitHub issue: https://github.com/actualbudget/actual/issues/2525 ### 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? ![Screenshot_2024-03-30_03-07](https://github.com/actualbudget/actual/assets/250466/5a7430fe-903b-4eb3-bc89-664a16f5f8f7) As you can see in the screenshot, I have a ton of entries like `PAYEE-NAME PAYEE-TXN-ID` like "AIRBNB 934274932". I would like to define "If payee starts with `AIRBNB `, then ..." but it's not possible. ### Describe your ideal solution to this problem Being able to use regular expressions or glob expressions like "starts with" and "contains" would allow for much more flexibility when defining a rule. ### Teaching and learning _No response_
GiteaMirror added the needs votesfeature labels 2026-04-26 02:44:05 -05:00
Author
Owner

@github-actions[bot] commented on GitHub (Mar 30, 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:2027965848 --> @github-actions[bot] commented on GitHub (Mar 30, 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 -->
Author
Owner

@jfdoming commented on GitHub (Mar 30, 2024):

I think you could use 'Imported Payee' instead of 'Payee' for a basic version of this (using contains)

<!-- gh-comment-id:2028166151 --> @jfdoming commented on GitHub (Mar 30, 2024): I think you could use 'Imported Payee' instead of 'Payee' for a basic version of this (using `contains`)
Author
Owner

@mattalxndr commented on GitHub (Mar 31, 2024):

@jfdoming I did see that, but my "Imported Payee" field is blank on these transactions. I imported them from a nYNAB dump. Maybe that needs its own Issue, I don't know.

<!-- gh-comment-id:2028645162 --> @mattalxndr commented on GitHub (Mar 31, 2024): @jfdoming I did see that, but my "Imported Payee" field is blank on these transactions. I imported them from a [nYNAB dump](https://actualbudget.org/docs/migration/nynab). Maybe that needs its own Issue, I don't know.
Author
Owner

@jfdoming commented on GitHub (Mar 31, 2024):

@jfdoming I did see that, but my "Imported Payee" field is blank on these transactions. I imported them from a nYNAB dump. Maybe that needs its own Issue, I don't know.

Huh, that should definitely have its own issue. It should be a copy of the initial value of 'Payee' normally

<!-- gh-comment-id:2028802261 --> @jfdoming commented on GitHub (Mar 31, 2024): > @jfdoming I did see that, but my "Imported Payee" field is blank on these transactions. I imported them from a [nYNAB dump](https://actualbudget.org/docs/migration/nynab). Maybe that needs its own Issue, I don't know. Huh, that should definitely have its own issue. It should be a copy of the initial value of 'Payee' normally
Author
Owner

@elkalt commented on GitHub (Sep 16, 2024):

I would be willing to try implementing this, but I have no experience with development on Actual. I can start taking a look early next week, but if someone could help point me in the right direction that would be appreciated :)

<!-- gh-comment-id:2353979529 --> @elkalt commented on GitHub (Sep 16, 2024): I would be willing to try implementing this, but I have no experience with development on Actual. I can start taking a look early next week, but if someone could help point me in the right direction that would be appreciated :)
Author
Owner

@jfdoming commented on GitHub (Sep 16, 2024):

I would be willing to try implementing this, but I have no experience with development on Actual. I can start taking a look early next week, but if someone could help point me in the right direction that would be appreciated :)

We have regex match on imported payee using the matches operator now! Does that fit your use case?

<!-- gh-comment-id:2354014873 --> @jfdoming commented on GitHub (Sep 16, 2024): > I would be willing to try implementing this, but I have no experience with development on Actual. I can start taking a look early next week, but if someone could help point me in the right direction that would be appreciated :) We have regex match on imported payee using the `matches` operator now! Does that fit your use case?
Author
Owner

@elkalt commented on GitHub (Sep 16, 2024):

@jfdoming That does, thanks!

<!-- gh-comment-id:2354056563 --> @elkalt commented on GitHub (Sep 16, 2024): @jfdoming That does, thanks!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#42674