github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-07 20:38:54 -05:00
Code Issues 1.6k Packages Projects Releases 55 Wiki Activity

[GH-ISSUE #195] "Create Rule" from payees modal does not add conditions #25916

New Issue
Closed
opened 2026-04-18 01:43:18 -05:00 by GiteaMirror · 10 comments
GiteaMirror commented 2026-04-18 01:43:18 -05:00
Owner
Copy Link

Originally created by @winklevos on GitHub (Aug 21, 2022).
Original GitHub issue: https://github.com/actualbudget/actual/issues/195

When using "Create Rule" button from the payees modal I would expect the rule to populate the condition for that payee. This doesn't occur, meaning you need to manually add it, the modal has no context so you would also need to remember the payee to search.

Browser: firefox
Version: https://hub.docker.com/r/kippenhof/actual-server
Confirmed the same behaviour locally building from master

image

image

I would expect
image

Originally created by @winklevos on GitHub (Aug 21, 2022). Original GitHub issue: https://github.com/actualbudget/actual/issues/195 When using "Create Rule" button from the payees modal I would expect the rule to populate the condition for that payee. This doesn't occur, meaning you need to manually add it, the modal has no context so you would also need to remember the payee to search. Browser: firefox Version: https://hub.docker.com/r/kippenhof/actual-server Confirmed the same behaviour locally building from master ![image](https://user-images.githubusercontent.com/30995408/185774002-040cef9e-9c4a-4e2f-aa07-2631a5d217ee.png) ![image](https://user-images.githubusercontent.com/30995408/185774022-2c5bab99-d028-499a-9830-7ca82cfd4a94.png) I would expect ![image](https://user-images.githubusercontent.com/30995408/185774064-e0263dc2-7adf-4c07-94ee-2727c4b0a83d.png)
GiteaMirror added the schedulesbug labels 2026-04-18 01:43:18 -05:00
GiteaMirror commented 2026-04-18 01:43:21 -05:00
Author
Owner
Copy Link

@rich-howell commented on GitHub (Aug 22, 2022):

Hey @winklevos

I am not sure this is a bug, but I will go ahead and mark it as such for the time being until it can be confrirmed either way.

Cheers

<!-- gh-comment-id:1222574794 --> @rich-howell commented on GitHub (Aug 22, 2022): Hey @winklevos I am not sure this is a bug, but I will go ahead and mark it as such for the time being until it can be confrirmed either way. Cheers
GiteaMirror commented 2026-04-18 01:43:21 -05:00
Author
Owner
Copy Link

@winklevos commented on GitHub (Aug 22, 2022):

Only reason I have the expectation it would populate is because there is a "create rule" button for each payee row. So seemed context bound.

Might be another UX thing if it was never intended

<!-- gh-comment-id:1223309574 --> @winklevos commented on GitHub (Aug 22, 2022): Only reason I have the expectation it would populate is because there is a "create rule" button for each payee row. So seemed context bound. Might be another UX thing if it was never intended
GiteaMirror commented 2026-04-18 01:43:21 -05:00
Author
Owner
Copy Link

@Kidglove57 commented on GitHub (Aug 23, 2022):

I am a bit puzzled. I have just entered two transactions in Actual for long standing payees and the category populated itself automatically - no problems. This is possibly becomes I am a long term user of Actual. My understanding has always been that Actual watches for a pattern over several transaction entries for a particular payee and only then starts to auto populate the category. Of course I never want an Amazon payee to do this because the category is different every time, so I manually switch it off for some payees (by setting the category in the rule to "nothing"). On a number of occasions I have also edited a particular payee to add the categorisation or note rule that I really want.

What I have not been able to find out is the exact logic for when a rule gets added to a payee. I just added the same new payee test transaction three times in a row and no rule was created so I am guessing it is more complex than that!

<!-- gh-comment-id:1223675726 --> @Kidglove57 commented on GitHub (Aug 23, 2022): I am a bit puzzled. I have just entered two transactions in Actual for long standing payees and the category populated itself automatically - no problems. This is possibly becomes I am a long term user of Actual. My understanding has always been that Actual watches for a pattern over several transaction entries for a particular payee and only then starts to auto populate the category. Of course I never want an Amazon payee to do this because the category is different every time, so I manually switch it off for some payees (by setting the category in the rule to "nothing"). On a number of occasions I have also edited a particular payee to add the categorisation or note rule that I really want. What I have not been able to find out is the exact logic for when a rule gets added to a payee. I just added the same new payee test transaction three times in a row and no rule was created so I am guessing it is more complex than that!
GiteaMirror commented 2026-04-18 01:43:22 -05:00
Author
Owner
Copy Link

@rich-howell commented on GitHub (Aug 23, 2022):

@Kidglove57 This is exactly how I understood that it worked, try creating a transaction for a fictional payee, I bet you don't get a rule created.

<!-- gh-comment-id:1223677879 --> @rich-howell commented on GitHub (Aug 23, 2022): @Kidglove57 This is exactly how I understood that it worked, try creating a transaction for a fictional payee, I bet you don't get a rule created.
GiteaMirror commented 2026-04-18 01:43:22 -05:00
Author
Owner
Copy Link

@Kidglove57 commented on GitHub (Aug 23, 2022):

Correct - and that is exactly what I was testing. Nor does it create a category for a payee I have only used once before. But no problem in overriding that if I want to - by adding a rule right away.

Sometimes I find it really annoying when auto categorisation takes place and I have to override it!

<!-- gh-comment-id:1223681172 --> @Kidglove57 commented on GitHub (Aug 23, 2022): Correct - and that is exactly what I was testing. Nor does it create a category for a payee I have only used once before. But no problem in overriding that if I want to - by adding a rule right away. Sometimes I find it really annoying when auto categorisation takes place and I have to override it!
GiteaMirror commented 2026-04-18 01:43:23 -05:00
Author
Owner
Copy Link

@winklevos commented on GitHub (Aug 23, 2022):

I think you're meaning to comment related to https://github.com/actualbudget/actual/issues/196.

This ticket is a UX thing unrelated to auto creation of rules

<!-- gh-comment-id:1223723964 --> @winklevos commented on GitHub (Aug 23, 2022): I think you're meaning to comment related to https://github.com/actualbudget/actual/issues/196. This ticket is a UX thing unrelated to auto creation of rules
GiteaMirror commented 2026-04-18 01:43:24 -05:00
Author
Owner
Copy Link

@Kidglove57 commented on GitHub (Aug 23, 2022):

Thank you for linking the two issues. Sorry for the confusion

<!-- gh-comment-id:1223726519 --> @Kidglove57 commented on GitHub (Aug 23, 2022): Thank you for linking the two issues. Sorry for the confusion
GiteaMirror commented 2026-04-18 01:43:24 -05:00
Author
Owner
Copy Link

@Kidglove57 commented on GitHub (Aug 23, 2022):

Returning to the issue actually raised here - I totally see the point made about the payee not auto populating when creating a rule relating to that payee. I agree that this would be expected behaviour. I see that there is the option to add multiple conditions ("is" or "one of") before applying any particular action so possibly this is an unintended consequence of the flexibility given by the rule structure?

<!-- gh-comment-id:1223780279 --> @Kidglove57 commented on GitHub (Aug 23, 2022): Returning to the issue actually raised here - I totally see the point made about the payee not auto populating when creating a rule relating to that payee. I agree that this would be expected behaviour. I see that there is the option to add multiple conditions ("is" or "one of") before applying any particular action so possibly this is an unintended consequence of the flexibility given by the rule structure?
GiteaMirror commented 2026-04-18 01:43:25 -05:00
Author
Owner
Copy Link

@carkom commented on GitHub (Feb 2, 2023):

I'm on version 23.1.12 with image ghcr.io/actualbudget/actual-server:latest and I am still experiencing this issue. Can anyone help?

<!-- gh-comment-id:1414079938 --> @carkom commented on GitHub (Feb 2, 2023): I'm on version 23.1.12 with image `ghcr.io/actualbudget/actual-server:latest` and I am still experiencing this issue. Can anyone help?
GiteaMirror commented 2026-04-18 01:43:26 -05:00
Author
Owner
Copy Link

@rich-howell commented on GitHub (Feb 2, 2023):

I'm on version 23.1.12 with image ghcr.io/actualbudget/actual-server:latest and I am still experiencing this issue. Can anyone help?

This will be available in the next release of Actual. You can find everything available in the current release, here https://actualbudget.github.io/docs/Release-Notes/

<!-- gh-comment-id:1414099938 --> @rich-howell commented on GitHub (Feb 2, 2023): > I'm on version 23.1.12 with image `ghcr.io/actualbudget/actual-server:latest` and I am still experiencing this issue. Can anyone help? This will be available in the next release of Actual. You can find everything available in the current release, here https://actualbudget.github.io/docs/Release-Notes/
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 schedules
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#25916
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?