Created attachment 150630 [details] A sample pivot table with multiple group fields Open the attached file, and filter any group field (Years, Quarters, ... , Fix date) to exclude everything but ">25.03.2021" or "<25.03.2019" (">12.10.2022" or "<20.09.2022" for last two groups). When the filtering is confirmed, all the data gets hidden from the table, and the pivot table naturally gets empty; but also all the group fields but the first one get hidden, too. If one had filtered some group field other than the first one, this filtered field would get hidden, too, making it impossible to easily change the filter back. It is currently impossible to use "Undo" to revert the action: while the data gets displayed after Undo, the filter is inaccessible (seems like an unrelated bug); but even if Undo worked, it is not always possible to use it: e.g., pivot table could turn into that state because of pre-existing filtering, which used to provide some data for the table; but after changing data in the source, and refreshing (possibly after saving and reloading), the new source does not provide any data for the table. It's impossible to undo a pivot table refresh; and closing unsaved could loose the work done thus far in this editing session. There is an obscure way to fix the table, though: one needs to change the table layout to make filtered field the first one. The behavior is very inconvenient, and also inconsistent e.g. with Excel, where all the fields are shown even when no data is displayed in the table. This is reproducible since version 3.6 (older versions would crash when filtering attempted).
Created attachment 150631 [details] Screencast of group field filtering bug
Repro Version: 6.2.3.1 (x64) Build ID: 9ba025bafb03b962c34687cf87806cc03a3a7436 CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win; Locale: es-ES (es_ES); UI-Language: en-US Calc: CL
Dear Mike Kaganski, 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
still repro in Version: 7.2.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 88ca6d7834a9d710dc124ee845fd3c270e33b59a CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: Skia/Raster; VCL: win Locale: ru-RU (ru_RU); UI: ru-RU Calc: threaded
Dear Mike Kaganski, 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://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Still Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 006b35d50024b1932d84380b5d2fec1f7066bccd CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded Jumbo
The following commit in 24.2 resolves a similar problem, but it actually doesn't solve the bug with the sample here: https://cgit.freedesktop.org/libreoffice/core/commit/?id=3551d18404cb19cdaa8edb170a549f5c5405d0cb