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 #1093] [Feature] Allow negating a rule conditon #7361

New Issue
Closed
opened 2026-04-10 17:09:14 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-10 17:09:14 -05:00
Owner
Copy Link

Originally created by @Jackenmen on GitHub (Jun 2, 2023).
Original GitHub issue: https://github.com/actualbudget/actual/issues/1093

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?

In rules, I'd like to be able to specify conditions that I would like to not be met in order for the rule to be applied.

For example, right now I'm often using the "contains" condition to match the first and last name of the imported payee such that I don't have to create rules for each way that their name may appear as in the imported transactions (which depends on the bank of both the recipient and sender). However, this falls short for two of my payees who share their last name and one's middle name is the other's first name.

Describe your ideal solution to this problem

What I want to do is simply add a "does not contain" condition for the first name of the other person so that their middle name doesn't get matched into the wrong payee but this is currently not a thing.

I think that it would be best to be able to just allow negating the condition but it might be easier to just add "is/does not" counterparts to each of the existing conditions.

Teaching and learning

If this would be implemented with counterparts then this is as discoverable as the regular conditions. If proper condition negation is added then I guess that there should be some kind of "NOT" switch before the select list in each condition.

Originally created by @Jackenmen on GitHub (Jun 2, 2023). Original GitHub issue: https://github.com/actualbudget/actual/issues/1093 ### 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? In rules, I'd like to be able to specify conditions that I would like to not be met in order for the rule to be applied. For example, right now I'm often using the "contains" condition to match the first and last name of the imported payee such that I don't have to create rules for each way that their name may appear as in the imported transactions (which depends on the bank of both the recipient and sender). However, this falls short for two of my payees who share their last name and one's middle name is the other's first name. ### Describe your ideal solution to this problem What I want to do is simply add a "does not contain" condition for the first name of the other person so that their middle name doesn't get matched into the wrong payee but this is currently not a thing. I think that it would be best to be able to just allow negating the condition *but* it might be easier to just add "is/does not" counterparts to each of the existing conditions. ### Teaching and learning If this would be implemented with counterparts then this is as discoverable as the regular conditions. If proper condition negation is added then I guess that there should be some kind of "NOT" switch before the select list in each condition.
GiteaMirror added the rulesneeds votesfeature labels 2026-04-10 17:09:14 -05:00
GiteaMirror commented 2026-04-10 17:09:15 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jun 2, 2023):

✨ Thanks for sharing your idea! ✨

This repository is now using lodash style issue management for enhancements. This means enhancement issues will now be closed instead of leaving them open. 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:1573378403 --> @github-actions[bot] commented on GitHub (Jun 2, 2023): :sparkles: Thanks for sharing your idea! :sparkles: This repository is now using lodash style issue management for enhancements. This means enhancement issues will now be closed instead of leaving them open. 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-10 17:09:15 -05:00
Author
Owner
Copy Link

@carkom commented on GitHub (Jul 11, 2023):

Fixed by #1287

<!-- gh-comment-id:1630516704 --> @carkom commented on GitHub (Jul 11, 2023): Fixed by #1287
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 needs votes rules
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#7361
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?