Description: Colour rendition of a filtered array with a conditional colour sort assigned to MOST of the cells in each row is corrupted when sorted on a column that has an alternate colour sort assigned to the column. Sample Calc file and .png example attached. Steps to Reproduce: 1. From the sample calc attached which is sorted on column [A] - the original natural data entry condition, observe the three colour sort applied to Cells C2:F10 together with the three colour sort applied to Cells O2:P10. 2. Sort on either column [O] or [P] and observe the corruption of colour scheme for C2:F10 Columns [Q:AC] are irrelevant to the conditional colour format and [AE:AH] only affect the identification of the "latest" column containing non-zero values Actual Results: Colour scheme of C2:F10 becomes corrupted - no longer reflecting the original Correct/Anticipated colour scheme for each row. O2:P10 is Correct/Anticipated. See attached .png. Expected Results: Colour scheme for each row of C2:F10 should remain unchanged from the unsorted condition as the data rows have not changed value - just location. Reproducible: Always User Profile Reset: No OpenGL enabled: Yes Additional Info: Version: 7.0.4.2 (x64) Build ID: dcf040e67528d9187c66b2379df5ea4407429775 CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: sv-SE (en_GB); UI: en-GB Calc: threaded
Created attachment 170298 [details] Sample Calc
Created attachment 170299 [details] Screen Grab
Perhaps I should have mentioned: I believe it worked correctly prior to this update of LO as the original .ods was exported to eXcel which still processes the colour scale correctly. I must also confess - I disposed of my original .ods and have simply opened the eXcel with LO and saved it as a .ods - which is now corrupting the colour scheme. either way - it's a bug in the Conditional Colour Formatting or the opening and saving of a fairly simple eXcel.
Another insight: I initially inserted a column between [C]&[D] to include more data so this may have "pushed" a change into the Colour Format Register but I have subsequently removed that column and executed a number of new saves with alternate names which made no difference to the error.
Another observation: Sorting on B,C,D,E or F produces further colour scheme variations
I have now observed: 1. Save and close the file whilst corruption is apparent. 2. Open the newly saved file. 3. Observe the corrected/consistent/desired colour scheme Conclusion: The colour scheme is corrected by the save > re-open process
As part of the resolution of another report, I have today replaced my profile. The bug is still apparent
I do reproduce the conditional colors in columns O and P disappear if sorting A2:AH10 by column O or P Version: 7.2.0.0.alpha0+ / LibreOffice Community Build ID: c088d26578d1be352efa49bd164a8217627648de CPU threads: 4; OS: Linux 5.7; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded
In order to reproduce the issue you need to sort first by column O and then by column P
Also reproduced in Version: 5.2.0.0.alpha0+ Build ID: 3ca42d8d51174010d5e8a32b96e9b4c0b3730a53 Threads 4; Ver: 5.7; Render: default; Locale: en-US (en_US.UTF-8)
Also reproduced in Version: 4.3.0.0.alpha1+ Build ID: c15927f20d4727c3b8de68497b6949e72f9e6e9e
and Version: 4.1.0.0.alpha1+ Build ID: a2c9d4f8bbde97f175bae4df771273a61251f40
Dear Colin, 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 a Bug @Xisco Fauli has previously verified all the way back to 4.1 I just attempted to prove 3 and can't even get it to function correctly. Some conflict over JRE which it initially demanded and then failed to find after installing it - even following a restart. None of the existing CF parameters appear in V3 CF - I'm not sure if that far back it even had the Manage function but as they were not present I wasn't presented with that option. Either the IFERROR() or INDIRECT() function which is part of the ColO processing fails with #NAME# Probably me/my installation but if defintive proof of a legacy error is required then somebody else needs to be resåponsible for that.