Bug 507400 - Category no longer populated when entering recurring transaction
Summary: Category no longer populated when entering recurring transaction
Status: RESOLVED DUPLICATE of bug 506625
Alias: None
Product: kmymoney
Classification: Applications
Component: ux-ui (other bugs)
Version First Reported In: 5.2.0
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-07-23 16:53 UTC by tneo
Modified: 2025-07-30 12:54 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description tneo 2025-07-23 16:53:36 UTC
SUMMARY
When you enter an entry that is similar to a previous entry, the category is no longer populated with values from the previous entry that is similar. #471210 appears related, but is different.

STEPS TO REPRODUCE
1. Create an entry in the ledger, for instance: payee Groceries with category Food
2. Save the entry
3. Make a new entry and enter the same payee. 

OBSERVED RESULT
The category is not populated (as it used to do) and the user needs to enter the field manually.


EXPECTED RESULT
Payee and category are linked and thus the tool populates the value upon entering the payee details.

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20250718
KDE Plasma Version: 6.4.3
KDE Frameworks Version: 6.16.0
Qt Version: 6.9.1
Kernel Version: 6.15.6-1-default (64-bit)
Graphics Platform: Wayland
Comment 1 Thomas Baumgart 2025-07-30 06:13:19 UTC
Are you talking about finding historic transactions based on the payee or the assignment of a default category? In case of the former other people are reporting it is working and opened a different issue (see bug #506625) in case of the latter I am unable to duplicate the problem.
Comment 2 tneo 2025-07-30 12:54:29 UTC
I had not found that issue. And it appears that I run into the same issue. Thus this can be closed.

*** This bug has been marked as a duplicate of bug 506625 ***