https://bugs.kde.org/show_bug.cgi?id=464636
--- Comment #4 from mau ---
OK, I just checked and it's correct that the transactions of accounts sharing
the same name are reported like "first account", "second account", so a human
can split them by analyzing the transaction dates. But I think
https://bugs.kde.org/show_bug.cgi?id=464636
--- Comment #3 from mau ---
Using the full hierarchy sounds like a very valid fix, since it would solve the
issue. The point is, it doesn't make sense to aggregate accounts with the same
name, if they are not the same, and I'm indeed interested in the
https://bugs.kde.org/show_bug.cgi?id=464636
--- Comment #2 from Jack ---
The same problem does not happen with Categories because in reports (at least
those I have checked) categories are listed with their full hierarchy, not just
the name of the lowest level category. I wonder if this might be
https://bugs.kde.org/show_bug.cgi?id=464636
--- Comment #1 from Jack ---
Please specify exactly where you see this behavior. I am only partly able to
replicate it.
If I run a Transaction by Accounts Report, with the Rows/Columns tab set to
organize by accounts, I do see 2022 listed only once,
https://bugs.kde.org/show_bug.cgi?id=464636
mau changed:
What|Removed |Added
CC||b-m...@gmx.ch
--
You are receiving this mail because:
