Bug 499210 - Missing accounts in report "transactions by account"
Summary: Missing accounts in report "transactions by account"
Status: RESOLVED FIXED
Alias: None
Product: kmymoney
Classification: Applications
Component: reports (other bugs)
Version First Reported In: 5.1.90
Platform: Other All
: NOR normal
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-01-27 18:44 UTC by Ralf Habacker
Modified: 2025-05-27 16:15 UTC (History)
0 users

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

Attachments
test file (10.78 KB, text/xml)
2025-01-27 18:44 UTC, Ralf Habacker 		Details
Screenshot from version 5.1.90 (186.79 KB, image/png)
2025-01-27 18:45 UTC, Ralf Habacker 		Details
Screenshot from version 4.8.5 (242.40 KB, image/png)
2025-01-27 18:46 UTC, Ralf Habacker 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Ralf Habacker 2025-01-27 18:44:56 UTC 
Created attachment 177723 [details]
test file

STEPS TO REPRODUCE
1. download kmymoney from https://cdn.kde.org/ci-builds/office/kmymoney/master/
2. start kmymoney 
3. load attached test file
4. Open report "Transactions by account (Customized - no conversion)"
4. Inspect report

OBSERVED RESULT
The "Investment ... (brokerage)" accounts are missing in the mentioned report

EXPECTED RESULT
The "Investment ... (brokerage)" accounts should be included in the mentioned report

SOFTWARE/OS VERSIONS
Operating System: openSUSE Leap 15.6
KDE Plasma Version: 5.27.11
KDE Frameworks Version: 5.115.0
Qt Version: 5.15.12
Comment 1 Ralf Habacker 2025-01-27 18:45:29 UTC 
Created attachment 177724 [details]
Screenshot from version 5.1.90
Comment 2 Ralf Habacker 2025-01-27 18:46:31 UTC 
Created attachment 177725 [details]
Screenshot from version 4.8.5

In the report generated by the kmymoney version 4.85 the brokerage accounts are included
Comment 3 Ralf Habacker 2025-05-27 16:15:02 UTC 
This problem could no longer be reproduced. It seems to have been fixed in the meantime.