Description: When manipulating conditional formatting in one of my sheets, I realised that I lost all the data (basically on the same amount of lines on which I'm applying or deleting the CF) in every other sheet (looks like just the ones before not after). The data above those lines stayed. I tried to check what kind of operation did that but couldn't solve it. Just noticed that it looks to be when I deleted some of the CF in the global list. I could reproduced it in an other file. Actual Results: Fill a first sheet with data let's say on 20 lines. Fill second one with 10 lines. I did it with numbers and applied conditional formatting with colour scale on each line so that 0 got red, 1 yellow and 2 green. Then try to modify the CF on some lines or go in the list and delete it for some lines. Expected Results: Go back to the first sheet and the 10 first lines should have been deleted. If you create more sheets (before the one you're applying CF), the data should disappear as well. Reproducible: Always User Profile Reset: No Additional Info: Well don't get why the CF on one sheet can have an impact on other sheets. I almost lost the data on a very important file because I was only working on this specific sheet without checking all the others before saving and closing. User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.168 Safari/537.36 OPR/51.0.2830.40
Created attachment 140173 [details] first sheet : loss of data, second sheet : where the CF is applied
5.1 is EOL, as 5.2 and 5.3.X versions. Please give a try to a recent LO version. Last stable one is 5.4.5 or even brand new 6.0.1
Thank you for reporting the bug. it seems you're using an old version of LibreOffice. Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Setting to RESOLVED WORKSFORME as the commit fixing this issue hasn't been identified.