Description: After File/App Close-Reopen Conditional Color Scale Formatting is no longer displayed. The entries are present in Manage but Editing has no effect. Have to be removed & recreated from scratch again( Steps to Reproduce: 0. https://picat.drycat.fr/Jiz8ZUnU/Qxcrkm0x.png 1. Format - Conditional - Color.Scale - (2 Entries) 2. File - Close - Open Actual Results: https://picat.drycat.fr/dNkbkJTD/nhgW3W2Y.png Expected Results: https://picat.drycat.fr/ehp1cbDH/4ZSORdQA.png Reproducible: Always User Profile Reset: Yes Additional Info: Version: 6.1.1.2 Build ID: 6.1.1-3 CPU threads: 2; OS: Linux 4.18; UI render: default; VCL: gtk2; Locale: en-US (en_US.UTF-8); Calc: threaded
I can not confirm with Version: 6.2.0.0.beta1+ Build ID: a63cd8bbe7cf881daa8dc7a7f32f3e5ac384e902 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3;
Created attachment 147208 [details] Reportedly, the problem is caused by R1C1 syntax (GIF produced by OP) However, in testing on Windows, I also used R1C1, and didn't repro (http://youtu.be/vcU6wxnhnX8?hd=1).
Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. (Please note that the attachment will be public, remove any sensitive information before attaching it. See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.) I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided.
*** Bug 121774 has been marked as a duplicate of this bug. ***
The temp workaround is to to switch to the Calc A1 formula syntax style, create that formatting, save it, reload the doc & then finally switch back to R1C1. That way it seems to persists..
Created attachment 147652 [details] Please attach a sample document, as this makes it easier for us to verify the bug..
> Thank you for reporting the bug.. Related bug in the attachment. R47R48. Merged cells never show conditional color scale properly.
CANNOT confirm here neither with A1 nor R1C1 syntax Version: 6.1.5.2 Build-ID: 1:6.1.5-3 CPU-Threads: 2; BS: Linux 4.19; UI-Render: Standard; VCL: gtk3; Gebietsschema: de-DE (de_DE.utf8); Calc: group threaded
Some of the Conditional Formatting settings will only save correctly in the .ods file format.
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.
Dear axettejoj-5397, 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 axettejoj-5397, 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