Description: When using conditional formatting, if an icon set is used with 3 icons (the default) and you set the 3 conditions to be <, =, and > of some value, saving and opening the document again changes all three conditions to >. I will attach some images to show this behavior more clearly. This happens when using the .ods file type. Steps to Reproduce: 1. make new calc document 2. make a column counting from 1 to 10 3. select that column, click conditional formatting, select "icon set..." 4. change all 3 boxes from "percent" to "value" 5. write 5 in all 3 boxes 6. change the first condition to < 7. change the second condition to = 8. change the third condition to > 9. press "ok", observe how the entire column is formatted as expected with icons 10. save document, close out of calc 11. open document, observe how only numbers 6-10 are formatted with an icon 12. re-open the conditional formatting that you set before and all 3 boxes are now set to > Actual Results: conditional formatting is not preserved when saving document Expected Results: file is saved properly Reproducible: Always User Profile Reset: No Additional Info: Version: 26.2.1.2 (X86_64) Build ID: 620(Build:2) CPU threads: 16; OS: Windows 11 X86_64 (build 26200); UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded
Created attachment 205829 [details] before saving and closing file
Created attachment 205830 [details] after saving and re-opening file
I believe this kind of bug has been already reported before, especially when "partially" editing each comparison, instead of completely finishing each comparison before continuing with the next. Anyway, although it should be easy to reproduce, please attach an ods file with the intended conditional formats, even if you cannot save the "correct, really intended" conditions. Please add some note within the ods file regarding which kind (or direction or color) of arrows were supposed to be displayed for each value/cell in the range where the conditional format is applied.
*** This bug has been marked as a duplicate of bug 163473 ***
*** This bug has been marked as a duplicate of bug 168439 ***