Bug 507245

Summary:	Offer past transactions after entering Payee even if amount was already entered
Product:	[Applications] kmymoney	Reporter:	Ingo Klöcker <kloecker>
Component:	general	Assignee:	KMyMoney Devel Mailing List <kmymoney-devel>
Status:	RESOLVED FIXED
Severity:	wishlist
Priority:	NOR
Version First Reported In:	5.2.0
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:	5.2.1
Sentry Crash Report:

Description Ingo Klöcker 2025-07-19 21:28:21 UTC

If one wants to make use of the past transactions for a payee one has to Tab past the two amount fields to the Payee field and enter the Payee. If one has "accidentally" already entered an amount past transactions are not offered when entering the Payee.

EXPECTED RESULT
Either the Payee field is placed before the two amount fields (which isn't ideal; I kind of like the new order of input fields) or entering the Payee still opens the past transaction list even if one has already entered an amount. Obviously, the new amount should not be overwritten by the amount of the selected past transaction.

Depending on which amount one has entered (either Payment or Deposit) the past transaction list could even offer only past transactions with a Payment or only past transactions with a Deposit.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: openSUSE Tumbleweed
KDE Frameworks Version: 6.16
Qt Version: 6.9.1

Comment 1 Jack 2025-07-19 21:49:08 UTC

Maybe some option(s) on listing past transactions.  In my case, I usually don't want to see them at all, even if I don't enter an amount.  My use case may be uncommon, but I often enter transactions without an amount (I don't know if explicitly entering $0 would help) but some note to myself in the memo field, and waiting for a list of possible matching transactions is just a waste of time for me.

Comment 2 Thomas Baumgart 2025-07-26 14:52:43 UTC

Is that still the case? I think this has changed lately so that the amount field can have a value and the selection of prior transactions is still shown.

Comment 3 Bug Janitor Service 2025-08-10 03:46:22 UTC

🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!

Comment 4 Ingo Klöcker 2025-08-12 19:29:25 UTC

Confirmed. It's fixed in version 5.2.1.