SUMMARY With the latest KMM AppImage (Version 5.0.80-5b599ce) when you enter a Tag within a split transaction the output in the report shows the transaction as having (No Tag).
STEPS TO REPRODUCE
1. Enter a split transaction in a Ledger and include appropriate Tag(s) in the split dialog. Leave the Tag field blank in the Ledger.
2. Open the Report Transactions by Tag
Transactions Tag within a split shows on the report as No Tag.
Transaction by Tag report should show Tags within Splits in the appropriate
Tagged grouping as selected in the split dialog.
Linux: Fedora 29
fyi This problem also exists in the Stable AppImage Version 5.0.3-4f18e69
The reason for this bug is the same as with bug 412429
A related problem might have been reported on the forum at https://forum.kde.org/viewtopic.php?f=69&t=163345
Git commit 73f0314c34aa2cbf0a532c282cc9acb28e104267 by Ralf Habacker.
Committed on 18/11/2019 at 10:44.
Pushed by habacker into tag '4.8.5'.
Fix 'Tags within Split transaction not reporting correctly'
M +25 -12 kmymoney/reports/querytable.cpp
Git commit 9bc5781d057b58a8a8dc465fda542d004927a513 by Ralf Habacker.
Committed on 13/12/2019 at 00:00.
Pushed by habacker into branch '4.8'.
Add support for showing tags on splits in tag report
M +21 -35 kmymoney/reports/querytable.cpp
Created attachment 127719 [details]
Here is a report of "Transactions by Tag" The transactions on 11/13/19 and 11/25/19 are parts of two split transactions with tags on the splits but not on the parent transaction.
Issue is still present in the latest AppImage 5.0.8-feb8f9e.
See attachment. The transactions on 11/13/19 and 11/25/19 are parts of two split transactions with tags on the splits, but no tag on the parent. The splits do not show up under the reports for their respective tags.
> Issue is still present in the latest AppImage 5.0.8-feb8f9e.
As can be seen from comment 5, a corresponding patch for 4.8 has been provided to the best of our knowledge. However, it is currently impossible to say whether this will not affect other reports.
For the 5.0 branch, due to the extensive changes that have been made, it is not possible to say whether the patch works at all and does not additionally break other reports.
This also applies to other changes for the reporting engine for https://phabricator.kde.org/D13803
(In reply to Ralf Habacker from comment #8)
> As can be seen from comment 5, a corresponding patch for 4.8 has been
> provided to the best of our knowledge. However, it is currently impossible
> to say whether this will not affect other reports.
There are two reasons for this:
1. due to the large number of report settings and the many enhancements and adjustments that have been made, the implementation of reports is in a state where adjustments and bug fixes are very susceptible to create hidden interference with other report types and variants, which may lead to deviations or missing results.
Since the core of financial applications is the "correct" (in the sense of defined rules) processing and presentation of figures, errors in reports have a huge impact and reduce the reliability and usability of the application.
2. In addition, there are currently no comprehensive tests that allow a developer to quickly determine whether a change to the report implementation will cause unwanted interference.
I can reproduce this issue. KMyMoney-5.1.0-74a8f0d-x86_64.AppImage, xubuntu 20.04
I discovered that the issue with Tags is more than a report problem and it's likely to be related to split Tags in general.
When there is a split transaction and there is Tags associated with them the split transactions are reporting wrong when viewing them in the Tags List within KMM.
The split transactions are properly recorded as a charge in my credit card account but when I view the split transaction in the Tags List it is showing as a Deposit which also reduces the balance by this amount.
Consequently the balance figure is reporting incorrectly.
Follow the steps in my post of 2019-04-10 and enter the transaction as a payment.
Then view the details of the post in the Tags List.