mirror of
https://github.com/actualbudget/actual.git
synced 2026-03-10 20:23:07 -05:00
[Bug]: Creating a new payee as part of creating a new rule fails #1705
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/actual#1705
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 @mullermn on GitHub (Dec 23, 2024).
Verified issue does not already exist?
What happened?
Having accidentally 'merged' a payee by applying a rule I was trying to recreate the original rule for future use. I type in the payee name for matching - this cannot automcomplete because the payee no longer exists. I selected 'Create new payee', but the payee that is created is not the one I requested, it is simply called 'new'.
How can we reproduce the issue?
Follow the workflow as described above, or shown here:
Create a rule for a payee that doesn't currently exist, and click 'Create Payee' when prompted
Observe that the payee that gets created has the wrong name
Validating that it's not just a graphical glitch from a separate view
Observe that the same thing has been happening previously
Where are you hosting Actual?
Pikapods
What browsers are you seeing the problem on?
Desktop App (Electron)
Operating System
Mac OSX
@pwinnski commented on GitHub (Dec 24, 2024):
I tested this in v24.11.0 and again in v24.12.0 using the desktop app on MacOS, as well as in v24.11.0 using the web UI, and in all three cases the created Payee was what I requested.
I get the same (successful) results whether I create the payee by clicking or hitting enter.
You didn't say; what version are you using?
@mullermn commented on GitHub (Dec 24, 2024):
Whatever PikaPods is currently on - which is client 24.9.0 and server 24.12.0 today.
Having tested more today I can refine the profile a bit further though - the bug doesn't happen if I use a 'Payee is' rule, but it does if I choose 'Payee one of'.
@sveselinovic commented on GitHub (Dec 24, 2024):
I can reproduce the bug on client version v24.12.0 locally, but only with "Payee one of", not with "Payee is", as described by the comment before.
This seems like a good first issue that I would like to tackle if nobody minds?
@pwinnski commented on GitHub (Dec 24, 2024):
Ah, yes, "Payee one of" is broken, I missed that in the first screenshot!
@sveselinovic It seems the way to get "dibs" on an issue is to create a PR. Other than that, they don't assign issues.