Created attachment 112783 [details] test document to reproduce the bug This was observed on Libreoffice 4.2.5 Linux (Ubuntu 14.04 stock installation), 4.3.5-rc2 Linux (libreoffice PPA) and 4.2.4.2 OS X (install from libreoffice website). See attached spreadsheet. Instructions: Select 2015 and 2016, and try to use the fill handle to autofill to the right until 2020. Result: Instead of copying the formatting - two cells joined for each year – and increasing the years, 2016 is repeated and then each year is inserted twice into every other cell. This happens with other combinations of merged/joined cells as well.
Hi @Jens, thanks for reporting. Reproducible: Win7x64 Version: 4.4.0.3 Build ID: de093506bcdc5fafd9023ee680b8c60e3e0645d7 Maybe the same problem than reported https://bugs.documentfoundation.org/show_bug.cgi?id=86143
Similar, but not identical. There are actually two bugs: 1. (#86143) complains about autofill results of merged cells not being merged too (even with workaround) 2. I also :) complain about the autofill results. If I select two cells I would expect the increment between these cells to be used for autofill increments, but Calc seems to do something different.
PS: If there's anything else I can do to help, please tell me! (And don't take "complain" in the previous comment too seriously.. I'm a heavy LO user and very much interested in getting as many bugs fixed as possible.)
(In reply to Jens from comment #3) > (And don't take "complain" in the previous comment too seriously.. I'm a > heavy LO user and very much interested in getting as many bugs fixed as > possible.) ;) Do you know if this worked correctly before, Jens?
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.0.5 or 5.1.0) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) http://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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2016-02-21
Hello, retested with LibreOffice 5.1.1.1, Build-ID: c43cb650e9c145b181321ea547d38296db70f36e CPU Threads: 8; OS Version: Mac OS X 10.11.3; UI Render: GL; Locale: de-DE (de.UTF-8) Result: Same bug behaviour as before. Not resolved. Sorry .. :)
Bug is also present on LibreOffice 3.3.0.4 (Mac).
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.2.5 or 5.3.0 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) http://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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170306
Still with Version: 5.3.1.1 (x64) Build ID: 72fee18f394a980128dc111963f2eefb05998eeb CPU Threads: 4; OS Version: Windows 6.19; UI Render: default; Layout Engine: new; Locale: es-ES (es_ES); Calc: group
** Please read this message in its entirety before responding ** 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Still present in this version: Version: 6.2.4.2 Build-ID: 1:6.2.4-0ubuntu0.18.04.1~lo1 CPU-Threads: 4; BS: Linux 4.15; UI-Render: Standard; VCL: kde5; Gebietsschema: de-DE (de_DE.UTF-8); UI-Sprache: de-DE Calc: threaded
Created attachment 166019 [details] testfile demonstrate planned fix, compared with excel
Created attachment 166020 [details] testfile demonstrate planned fix, compared with excel (xlsx)
Created attachment 166021 [details] screenshot of planned fix vs excel
A suggested fix is uploaded to gerrit: https://gerrit.libreoffice.org/c/core/+/103765 LO will handle these cases a bit better as excel do. The uploaded test files, and screenshot, demonstrate this.
Attila Szűcs committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/03dfa09886b6fd0ebda7abe7d5e142da172e8cc2 tdf#88782 sc: autofill number sequences in merged cells It will be available in 7.1.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
verified in Version: 7.1.0.0.alpha0+ (x64) Build ID: a883002d8e2fd77f80c43b7b2e6ac329d83d929d CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: Skia/Raster; VCL: win Locale: ru-RU (ru_RU); UI: ru-RU Calc: threaded hmmm, Attila will you plan to do something else here or we can close it as FIXED?
thx Roman, i forgot to close the ticket. I plan to do some follow-up commits for different value types like date.. but they will be in separate bug tickets.