After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 626385 - Transaction Report Sorting + Grouping
Transaction Report Sorting + Grouping
Status: RESOLVED OBSOLETE
Product: GnuCash
Classification: Other
Component: Reports
2.2.x
Other All
: Normal enhancement
: ---
Assigned To: Andreas Köhler
Andreas Köhler
: 788150 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2010-08-08 19:20 UTC by Tarlika Elisabeth Schmitz
Modified: 2018-06-29 22:42 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Confirm this unsorted date issue (135.22 KB, image/png)
2017-09-19 14:15 UTC, Chris
Details

Description Tarlika Elisabeth Schmitz 2010-08-08 19:20:18 UTC
The Transaction Report Sorting tab combines sorting and grouping of transaction, which should be separate for greater flexibility and eliminate the inconsistent behaviour I describe below.

1) When choosing "Other Account Name" as Secondary Key, the transaction report will produce level 2 headings and totals. Secondary Sort Order relates to level 2 headings. But there is no means of sorting the transactions within the group! This is rather annoying as there is no recognizable sort order. At least I would expect them to be sorted by date.

2) When choosing "Description" as Secondary Key this is interpreted as transaction sort order and no level 2 grouping is generated.

I would like to propose to have separate tabs for sorting and grouping: on the latter the user can choose whether or not to display level 2 and if so in which manner to sort level 2 headings and whether to display level 2 subtotals.

On the Sorting tab the user can choose how to sort transactions within the group.

Also, terminology on the Easy stylesheet configuration should be consistent with the terminology used on the Transaction Report tabs.
Comment 1 Christian Stimming 2010-08-13 09:15:32 UTC
Your version is rather old. Can you check again with the 2.2.9 version, which (I think) already has improvements in that area? Or even one of the unstable 2.3.x versions, which might have even more improvements?
Comment 2 Tarlika Elisabeth Schmitz 2010-08-13 09:59:20 UTC
I run the current Debian stable release. The next release, which is just around
the corner, will include 2.2.9. I will have to wait another 1-2 years till I
get 2.4. Therefore I won't be able to comment on the latest changes.

I was hoping that my suggestion/description was clear enough for someone else, who has a newer release, to follow.
Comment 3 David Carlson 2012-08-13 19:00:38 UTC
I did some testing using version 2.4.11 in Windows 7.

What I see in this version is that there is no grouping at all, just sorting with one or two exceptions.  The subtotal selection boxes have no effect other than adding some lines to the output when some sort key combinations are selected.  One exception is when the primary sort key is Date, then the Primary Subtotal for Date Key works and subtotals appear correctly.

There is no logic to exclude inconsistent, redundant or pointless combinations of primary and secondary sort keys.  The 'other account' sort keys do not make sense when transactions have splits.  The sort is by 'Split' in that case.  Only meaningful secondary sorts should be permitted with each primary sort key choice.  An example of meaningful sort combinations would be to have a primary sort by Account and a secondary sort by Date, Description or Amount.

As Tarlika Elisabeth Schmitz proposed, grouping (with subtotals) should be handled separately from sorting.  Subtotal check boxes should not appear in the sorting tab.  Subtotals should only appear when grouping is selected.  
Only meaningful secondary groups should be permitted with each primary group choice.  An example of meaningful group combinations would be to have a primary group by Date and a secondary group by Account or Description.

Continuing with her proposal, sorts within primary and secondary groups should be separately selectable, with only meaningful combinations allowed.
Comment 4 Chris 2017-09-19 14:14:18 UTC
Looking through this bug report.
Confirm using current transaction report:
If "Primary SortKey" is date, primary subtotal e.g. Quarterly
And "Secondary SortKey" is account name/code, subtotal is ticked,

The report is showing some incorrect grouping. Screenshot attached.
Just wished to confirm this apparent bug.

I'll look into this.
Comment 5 Chris 2017-09-19 14:15:42 UTC
Created attachment 360048 [details]
Confirm this unsorted date issue
Comment 6 John Ralls 2017-09-25 20:03:02 UTC
*** Bug 788150 has been marked as a duplicate of this bug. ***
Comment 7 John Ralls 2018-06-29 22:42:39 UTC
GnuCash bug tracking has moved to a new Bugzilla host. The new URL for this bug is https://bugs.gnucash.org/show_bug.cgi?id=626385. Please continue processing the bug there and please update any external references or bookmarks.