Description: menu Format - Rows - Show or context menu Show rows displays rows hidden by a filter - this is a property or an error. Rows remain hidden in MSO. Actual Results: rows are show Expected Results: rows should remain hidden Reproducible: Always User Profile Reset: No Additional Info:
I think not a bug it just does what is required, show the rows, if in MSO does nothing then what it's their function?
I think Hide rows and filter are two different options. Show rows should only show rows hidden by Hide rows.
MSExcel doesn't show rows hidden by filter when I select Show rows in this case. Heiko, Eike, any opinions?
Hidden rows/columns are shown per "Show columns" (or rows), where the user needs to select the hidden cells (A..C if B is hidden, or 1..3 in case of 2, or 1 for B, or A for 2). The autofilter function _hides_ rows ($A != 2 for example). If now A is being selected and Format > Rows > Show executed, the filtered row is shown but the filter setting remains in place. So this is definitely a bug (likely a dup). The issue could be solved by making a difference between filter and visible, probably solving some other bugs. OTOH it opens the door for new confusion when these two options are combined by the user. @QA: Missing a META ticket on (auto) filter issues.
For me it's a great utility of how it works now, the ability to show some of the filtered rows without the need to re-elaborate the filter, what some times would be very difficult. Looks to me it is an improvement not a bug. The filter it's not destroyed, so can be reapplied without rebuild it.
Dear kabilo, 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 reproducible on current master. In my opinion, this is apparently a bug. The rows filtered-out by autofilter should only be shown by resetting the autofilter. The rows should not show by changing the row height (as in bug 36383) or by clicking the "Format > Row > Show". "Format > Row > Show" is used to show up the hidden rows (right-click on row header > Hide). Filtered rows are not normal hidden rows.
Reproduced on daily master build. To clarify on steps to reproduce: 1. Add data to any column 2. Data > Autofilter 3. Filter out any rows within the column 4. Select the whole column 5. Format > Rows > Show Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 9a37652b79001bf5208841b9221dee851b9b6d0f CPU threads: 6; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded
Reproduced on LO v. 3.3.0
Dear kabilo, 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