Description: Every time you close and open a calc Spreadsheet some of the conditional formatting breaks. It breaks however in many different ways: - Data Bars usually break either to display all cells 100% or all cells 0% - Every other condition just stops displaying. Features: You can edit the condition but it never updates. You can even change the Cell range the display will stay the same. Only deleting and recreating it makes the condition work again. I have copied whole sheets with different conditions over to a new sheet to see if that helps. To my surprises, some conditions startet working again in the new sheet, others didn't Conclusion: This is all kinds of fucked up, so that I can't even make a coherent bug Report :O Steps to Reproduce: 1. Make a conditional formatting 2. Safe and close the Spreadsheet 3. Reopen the Spreadsheet. 4. be lucky (bug is random) 5. Enjoy Actual Results: Chaos. Some Conditions are properly displayed some are not. And there aren't changable. Expected Results: Conditions display the same after closing and reopen. Reproducible: Sometimes User Profile Reset: No Additional Info: none
This is not version specific. I had this bug since forever. Since I started using LibreOffice a few years ago.
Created attachment 161066 [details] Bugged Conditional Formattings after reopen column A is a data bar and bugged column B is a condition and is ok column F is a data bar and bugged
Created attachment 161067 [details] Bugged Conditional Formattings after reopen columns A condition got moved to C. Changes didn't work conditional formating bugged
Created attachment 161069 [details] Bugged Conditional Formattings after reopen The whole sheet got copied to a new sheet with: -select all -copy -paste Only a few conditions made it over. Column G started working in the new sheet.
Comment on attachment 161066 [details] Bugged Conditional Formattings after reopen Conditional formatting in column A B F and G column A is bugged at 100% column B is a condition an is ok column F is bugged at 1% column G is bugged at 1%
Sorry I'm not too familiar with Bugzilla and the comments are not very intuitive to me. So I commented on the attachments twice.
Here is another little fun info. I tried saving the file with the working conditions in different file formats. This is what happend: .fods and .ods column A and F is bugged colum B and G is fine .xlsm column A F and G are fine column B is bugged .xlsx (Excel) All columns are fine (lol wut) .xlsx (Office Open XML Spreadsheet) column A F and G are fine column B is bugged
What's version of LibreOffice do you use? Please write info from Help->About dialog here
(In reply to Roman Kuznetsov from comment #8) > What's version of LibreOffice do you use? Please write info from Help->About > dialog here Please comment on this and attach an example document. Set to NEEDINFO. Change back to UNCONFIRMED after you have provided the document.
Sorry after a month I did not check for updates on this bug. I can't recall wich version I used then. I will try and reproduce with current version
[Automated Action] NeedInfo-To-Unconfirmed
Dear e688497, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear e688497, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp