https://bugs.kde.org/show_bug.cgi?id=470384
--- Comment #4 from Jack <ostrof...@users.sourceforge.net> --- When replying to a bug by email, please send JUST your new comments. Your entire email becomes the next comment to the bug, so quoting a previous comment just clutters up the display. You can also keep all discussion with the bug; I don't need separate emails. Minor suggestion, stick to simpler attachments, I find yours somewhat difficult to follow. Main point, I can easily reproduce the problem, using a version compiled from the head of the 5.1 git branch. I will now need to look into the code to see how easy it will be to fix. The problem does NOT occur in a version compiled from master branch. so even if we do nothing now, this will be fixed in 5.2. There is no set timeline for this. In terms of why the html export doesn't show the problem, I'll have to look in the code to see the differences in generating the csv and the html. The html is specifically intended to look like the report in the application where the csv is intended to export the data for further reporting or analysis, although I don't see any reason to intentionally omit a useful label. Some additional information: the top level grouping of reports in the Reports View is not the same as the internal grouping by implementation type. I think this problem probably occurs with all the transaction reports when grouped by something such as category, although these reports appear in several of the report groups. The reports in the tax group is identical to other reports, just with an added filter of only transactions for categories marked as being tax related. (I have a suspicion that tax filter is causing some problems by itself, that is best kept separate from this, more basic issue.) -- You are receiving this mail because: You are the assignee for the bug.