Created attachment 117118 [details] Sample workbook with data and multiple demonstroatin pivottables Sorry, but there may be multiple issues rolled into this. -I'm also aware that Pivottables are typically for brave souls only. This arose in assisting a user with an existing Pivottable, but I have replicated with a simpler example. Original issues were on 4.3.5.2, detailed testing done on 4.4.3.2 (both windows). The attached example sets out to create grouped columns of 'category', and then drill to details within these. Step 1: Basic table with 'Category' in Columns, 'Type' in Rows, and Value in data. Issue 1: Enable Drill to Details hidden and unchecked by default. IME Drill to details is fairly standard expected behaviour - is there a performance advantage to disabling it? Once 'Enable Drill to Details' is checked, drilling works as expected prior to any grouping being attempted. Step 2: Attempt to Group the columns so that a1,a2,a3 are together, b1,b2,b3 are together. -Select column headings a1,a2,a3 and then Data>Group and Outline>Group Issue 2: Grouping does not work AT ALL if the 'Category' field is beneath the 'Data' field in the 'Edit Layout' dialog (which is the only place you can place it. To remedy this you need to either demote or delete the 'Data' field. The sheet 'Pivot Table_Data_1' has been left in the ungroupable state. The sheet 'Pivot Table_Data_2' has been fixed by removing the 'Data' field Step 3: Drill to details -Double-click on values in sheet sheet 'Pivot Table_Data_2' to show rows of original data in new sheet Issue 3: Cannot drill into values in a non-grouped column. In the example sheet 'Pivot Table_Data_2' categories a1/a2/a3 and b1/b2/b2 are each grouped and category c1 is not grouped. No groups are collapsed. Double-clicking on Cell B4 will not drill. Cell C4 will drill. The sheet 'Pivot Table_Data_3' is a direct copy of sheet 'Pivot Table_Data_2', except with category c1 grouped (into a group of 1). Issue 4: Attempt to rename Group causes Group to vanish. The sheet 'Pivot Table_Data_4' is a direct copy of The sheet 'Pivot Table_Data_3'. I edited Cell B2 which contained the header for Group1, to attempt to rename it 'Group of A'. At this stage the entire group of records disappears.
Confirming all 4 issues. They should probably be opened as individual issues, even though they may be related. Issue 4 is the most serious one, since it hides data which should be shown, with no obvious way to get the data to show again - undo does not work, which is probably a separate issue.
(In reply to Nis Jørgensen from comment #1) > Confirming all 4 issues. They should probably be opened as individual > issues, even though they may be related. > > Issue 4 is the most serious one, since it hides data which should be shown, > with no obvious way to get the data to show again - undo does not work, > which is probably a separate issue. Thanks Nils. Would you like me to re-submit 2/3/4 as separate bugs?
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.1.5 or 5.2.1 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) http://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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20160920
Confirming all 4 issues in LO 5.1.4.2 on Gentoo Linux. Unfortunately, neither 5.1.5 nor 5.2.1 are available as binaries for Gentoo yet. The sample workbook does not seem to contain all the sheets mentioned in the accompanying comment, however.
Confirming issue 4 (group disappears on rename) for LO 5.2.7.2 on Debian Linux, though I found that refreshing the pivot table will make the group re-appear (with its new name). Perhaps a pivot table refresh could be done automatically after a user renames a group? In case it is undesirable to refresh the pivot automatically (because it cannot be undone), perhaps a message to the user that he needs to refresh the pivot himself to see the renamed group again?
I confirm issue 4 on LO 6.0.0 on Windows 10 and Ubuntu 17.04. Editing pivot table layout make it re-appear with correct group name.
** Please read this message in its entirety before responding ** 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 http://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
Hi - have taken the time to test using Version: 6.0.5.2 Build ID: 00m0(Build:2) CPU threads: 4; OS: Linux 4.12; UI render: default; VCL: kde4; Locale: en-NZ (en_US.UTF-8); Calc: group I can confirm that Issue 4 in my original report is now fixed - Thanks! Issues 1-3 remain. Thanks, Alex
Also confirming that Issue 4 is fixed. Thanks Dimitri Bouron for fixing this! (see bug 111305) Version: 6.1.2.1 Build ID: 1:6.1.2-1~bpo9+1 CPU threads: 2; OS: Linux 4.17; UI render: default; VCL: gtk3; Locale: en-US (en_US.UTF-8); Calc: group threaded
Dear alex, 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 http://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
Dear alex, 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
Dear alex, 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