Created attachment 166934 [details] example with manually set date start and interval Open attached document in Excel and in LibreOffice. The first date category is set to 2019-12-31, the main grid to 1 month. With this setting you get the non existing date 31.Feb.2020. Excel resolves non existing dates so that it uses the next previous date in that month, and use the original day number for the next months. LibreOffice resolves a non existing date so, that it goes a distance forward as if 31.Feb.2020 exists but use the really existing date then. For further months this new date it taken as start. I think, that the way Excel does it, is the better way. I come along this problem, when discussing the still open issue https://issues.oasis-open.org/browse/OFFICE-2119 in the OASIS ODF TC.
Created attachment 166995 [details] Comparison LibreOffice 7.1 master and MSO 2010
Hi Regina, Not sure if I can reproduce what you reported, see the attached comparison.
(In reply to Xisco Faulí from comment #2) > Hi Regina, > Not sure if I can reproduce what you reported, see the attached comparison. The comparison shows it clearly. Look at the position of the main grid and the date labels at the date axis. LO has 2018-12-31, 2019-01-31, 2019-03-03, 2019-04-03 Excel has 2018-12-31, 2019-01-31, 2019-02-28, 2019-03-31, 2019-04-30 So Excel keeps the major grid being at the last day of the month.
Conforming behavior in: Version: 7.2.0.0.alpha0+ (x64) Build ID: 796c7f612603490dda9277ced0f6ab3cce3bc116 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: default; VCL: win Locale: en-US (hu_HU); UI: en-US Calc: CL
Dear Regina Henschel, 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
I see the difference still in Version: 7.5.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 17dfc9a9da009cc23d2222e3fb4e2cef9c97d581 CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: de-DE (en_US); UI: en-US Calc: CL threaded