Created attachment 149902 [details] Example file from Calc with pivot table When creating a pivot table and trying to change the data field sort order, the order is not changed unless a different sort criteria is selected too. Steps to reproduce: 1. Create a simple data table, 3x3 in Calc 2. Select all the data and create a pivot table from it 3. Set two columns (Year and Sales in my example) of the three as Row Fields in the Pivot Table Layout Window and the third as Data Fields 4. Double click on the first row field (Year in my example). The Data Field window opens. 5. Click Options in the Data Field window 6. Next to the Sort by dropdown, select Descending instead of the default Ascending. Do not select the Manual option, that one seems to work :). 7. Close the Data Field Options window by clicking OK and the Data Field window too. 8. Reopen the Data Field and Data Field Options window. Notice that the sorting order is still Ascending, despite the former selection. 9. Now in the Sort by dropdown select a different option (Sum – Expenses in my example) and select the Descending option. 10. Close the Data Field Options window by clicking OK and the Data Field window too. 11. Reopen the Data Field and Data Field Options window. Notice that the sorting order is now changed to Descending. Actual results: The sort order is not changed from Ascending to Descending (or vice versa) without changing the row field used for sorting. Expected results: The sort order should be changed without changing the row field used for sorting. LibreOffice details: Version: 6.3.0.0.alpha0+ Build ID: 65438bcda46bab4f2fe6fb555f44aace45e11e5e CPU threads: 4; OS: Windows 6.3; UI render: GL; VCL: win; Locale: hu-HU (hu_HU); UI-Language: en-US Calc: threaded Also happens with: Verzió: 5.4.0.3 Build az.: 92c2794a7c181ba4c1c5053618179937228ed1fb CPU szálak: 4; OS: Windows 6.2; Felületmegjelenítés: GL; Területi beállítások: hu-HU (hu_HU); Calc: CL Verzió: 4.4.7.2 Build az.: f3153a8b245191196a4b6b9abd1d0da16eead600 Területi beállítások: hu_HU Verzió: 4.2.0.4 Build az.: 05dceb5d363845f2cf968344d7adab8dcfb2ba71 But not with: Verzió: 4.1.0.4 Build az.: 89ea49ddacd9aa532507cbf852f2bb22b1ace28 Verzió: 4.0.0.3 (Build az.: 7545bee9c2a0782548772a21bc84a9dcc583b89) LibreOffice 3.5.0rc3 Build ID: 7e68ba2-a744ebf-1f241b7-c506db1-7d53735
Created attachment 149903 [details] Screenshot of the problem in Calc
Thank you for reporting the bug. I can confirm the bug present in Version: 6.3.0.0.alpha0+ Build ID: b6b28931435e44aca92b8c0e1659f701e3ed1a87 CPU threads: 2; OS: Windows 6.1; UI render: default; VCL: win; TinderBox: Win-x86@42, Branch:master, Time: 2019-01-30_06:57:04 Locale: en-US (en_US); UI-Language: en-US Calc: threaded
Bibisected with win32-4.3 to https://gerrit.libreoffice.org/plugins/gitiles/core/+/7e491281d2ba71490fa22cce1e43ba91f60395e3^!/ fdo#69984: Handle duplicate field names correctly. Had to skip a few commits, but luckily it did not matter.
Dear Gabor Kelemen, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
*** Bug 154408 has been marked as a duplicate of this bug. ***
I'm the guy who filed bug #154408 with a reference to this bug. I understand that my bug report was then marked as a duplicate of this one, but I want to emphasize that I only decided to file a new bug because comment #4 here gave me the impression that no one would give this report any attention. I really appreciate the work of the LibreOffice project, but I'm disappointed that this bug report has been allowed to catch dust for more than four years. Not being able to sort pivot tables properly is a pain, I consider this to be quite basic functionality. I hope this could be given some more priority?
(In reply to Alexander van Loon from comment #6) > I'm the guy who filed bug #154408 with a reference to this bug. I understand > that my bug report was then marked as a duplicate of this one, but I want to > emphasize that I only decided to file a new bug because comment #4 here gave > me the impression that no one would give this report any attention. > > I really appreciate the work of the LibreOffice project, but I'm > disappointed that this bug report has been allowed to catch dust for more > than four years. Not being able to sort pivot tables properly is a pain, I > consider this to be quite basic functionality. I hope this could be given > some more priority? Please have patience and keep in mind we have over 15 thousand reports in NEW status at the moment.
Found same problem in 7.4.7.2