[GH-ISSUE #279] Duplicate payees should be prevented #6941

Closed
opened 2026-04-10 16:35:53 -05:00 by GiteaMirror · 2 comments
Owner

Originally created by @MikeBishop on GitHub (Nov 15, 2021).
Original GitHub issue: https://github.com/actualbudget/actual/issues/279

The "Create Payee Foo" item still appears in the payee list when a payee named Foo exists. Selecting it creates a second, identically-named payee. The option to create a new payee should disappear if what's typed exactly matches an existing payee. (Or, since I assume there's some trimming/normalization in that flow, if the created payee would have the same name as an existing payee.)

Originally created by @MikeBishop on GitHub (Nov 15, 2021). Original GitHub issue: https://github.com/actualbudget/actual/issues/279 The "Create Payee Foo" item still appears in the payee list when a payee named Foo exists. Selecting it creates a second, identically-named payee. The option to create a new payee should disappear if what's typed exactly matches an existing payee. (Or, since I assume there's some trimming/normalization in that flow, if the created payee would have the same name as an existing payee.)
GiteaMirror added the can’t replicate label 2026-04-10 16:35:53 -05:00
Author
Owner

@MikeBishop commented on GitHub (Mar 8, 2022):

Probably related: Typing "F" and hitting "Foo" in the keyboard's autocomplete does not match a payee named "Foo", because what's typed into the field is "Foo ". Actual should trim leading and trailing whitespace from the contents of the field before deciding whether the Payee exists.

<!-- gh-comment-id:1280035624 --> @MikeBishop commented on GitHub (Mar 8, 2022): Probably related: Typing "F" and hitting "Foo" in the keyboard's autocomplete does not match a payee named "Foo", because what's typed into the field is "Foo ". Actual should trim leading and trailing whitespace from the contents of the field before deciding whether the Payee exists.
Author
Owner

@rich-howell commented on GitHub (Oct 17, 2022):

Hey @MikeBishop

This issue is quite old, I am sorry about the delay in getting back to you, I don't think this is an issue anymore, I couldn't replicate it.

If the issue is still occuring, please let me know and I will re-open this for investigation

Cheers
Rich

<!-- gh-comment-id:1281244657 --> @rich-howell commented on GitHub (Oct 17, 2022): Hey @MikeBishop This issue is quite old, I am sorry about the delay in getting back to you, I don't think this is an issue anymore, I couldn't replicate it. If the issue is still occuring, please let me know and I will re-open this for investigation Cheers Rich
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#6941