Created attachment 140917 [details] Sample with grouped rows Open the attached sample sheet with rows 11-20 grouped and collapsed. Remove grouping of rows. => Rows 11-20 remain hidden. While it's true that a collapsed group is hidden, when grouping is removed, I would expect the group effect (ie. the collapsing) to be removed as well. Observed using LO 6.0.2.1 & 3.3.0 / Ubuntu 17.10.
Seems it happens collapsing while in a cell of colapsed rows and without move from there then ungroup.
> Remove grouping of rows. Data - Group and Outline - Group... > => Rows 11-20 remain hidden. > While it's true that a collapsed group is hidden, when grouping is removed, > I would expect the group effect (ie. the collapsing) to be removed as well. If I understand, first you hid the rows than grouped, than ungrouped and you expect them to be also shown/unhidden. I don't see why or you didn't explain how sample was created. So I don't agree with New.
(In reply to Timur from comment #2) > If I understand, first you hid the rows than grouped, than ungrouped and you > expect them to be also shown/unhidden. > I don't see why or you didn't explain how sample was created. > So I don't agree with New. You're right, I could've been clearer. In my defense, "rows 11-20 grouped and collapsed" contains an ordering, and it seemed to be the only obvious way. Note how once you hide rows 11-20, you can't group them, because you have to select the first and last row to be grouped, and they're all hidden.
OK. 1. group rows 11-20 via Data - Group and Outline - Group... 2. optionally hide rows 14-16 3. collapse grouped rows 11-20 via "-" or Data - Group and Outline - Hide Details 4. expand grouped rows 11-20 via "+" or Data - Group and Outline - Show Details see that all rows are shown 5. optionally hide rows 17-19 6. collapse grouped rows 11-20 again 7. remove grouping of rows via Data - Group and Outline - UnGroup... see that all rows 11-20 remain hidden Expected: rows 11-20 are shown and don't remain hidden Note: it could be better that rows 17-19 remain hidden but doesn't seems possible with the current logic of hiding and showing grouped rows.
** 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
Still buggy in LO 6.3.0.0.alpha0+ (cc9a8c13dad6f3d82a2386554bd6113b486a1752) / Windows 7.
Dear Aron Budea, 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
Repro 7.3+
*** Bug 142736 has been marked as a duplicate of this bug. ***
Dear Aron Budea, 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
Version: 7.4.7.2 (x64) / LibreOffice Community Build ID: 723314e595e8007d3cf785c16538505a1c878ca5 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: sv-SE (en_GB); UI: en-GB Calc: threaded Still present Not much more than a cosmetic issue as the rows (or columns) can simply be unhidden with right click on the selected adjacent header segments and "show rows"
Repro 24.8+