Created attachment 175614 [details] ODS file demonstrating the bug The error occurred in an ODS file being edited the last time with LO 6.1.5 when the behavior was as I expected. I have a list of data where in the first column are timestamps and other data right to it. I created a conditional format to create a border on the top if the difference of the timestamp in the first column to the one in the row above is above a limit (to make lines between the days). The timestamps are all formatted with "DD.MM.YY hh:mm" (done by LO automatically on input). In the first cell of a day, starting with LO 7.0.4.2 (not having tried any version between 6.1.5 and 7.0.4.2!) the cell formatting is ignored and the value is displayed as a number.
Created attachment 175615 [details] Screenshot how the bug looks in LO 7.0.4.2
Created attachment 175616 [details] Screenshow how the file looks in LO 6.1.5.2
This seems to have begun at the below commit. Adding Cc: to Eike Rathke; Could you possibly take a look at this one? Thanks c3dc960a90a62f0343f99cc63f4e446ea8292426 is the first bad commit commit c3dc960a90a62f0343f99cc63f4e446ea8292426 Author: Jenkins Build User <tdf@pollux.tdf> Date: Sun Oct 27 00:18:08 2019 +0200 source 2b0626161d3ef7c4a51007018d13ec391d3a2b04 https://git.libreoffice.org/core/+/2b0626161d3ef7c4a51007018d13ec391d3a2b04
In attachment 175614 [details] from comment 0, the conditional format uses the "Untitled2" style, which has the "General" number format. Before LO 7.0, the base direct format is modified only by applying the border in the "Untitled2" style. Since LO 7.0, the base direct format is basically avoided/ignored when the conditional format is applied, and so the number format from the "Untitled2" style completely overrides the "date" direct format. IDK whether this was done on purpose for LO 7.0, or this is some unwanted consequence of some other decision/change. I guess only Eike can answer that(?).
Dear armin, 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
(In reply to QA Administrators from comment #5) > Dear armin, > > 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/ The latest version I can test with reasonable effort is 25.2.2.2 > If the bug is present, please leave a comment that includes the information > from Help - About LibreOffice. The bug is still reproducible, here are the details of the version: Version: 25.2.2.2 (X86_64) / LibreOffice Community Build ID: 520(Build:2) CPU threads: 1; OS: Linux 6.12; UI render: default; VCL: x11 Locale: de-AT (de_AT.UTF-8); UI: en-US Debian package version: 4:25.2.2-1 Calc: threaded > 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 Even the commit having caused this error is already documented here in the comment from: 2022-07-29 21:41:09 UTC, so this part doesn't make sense in this context. > 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