Description: In the attached .ODS file: Sheet1 has some data, note that the 1st column of the 3rd row is blank. Sheet2 contains SUMIF function which has reference to Sheet1. This function is showing 0 value which is correct and is the same as other office suites. However when copy Sheet2 to a new file, the SUMIF function returns wrong result. Steps to Reproduce: 1. Copy "Sheet2" to a new file (right-click on the sheet name tab, then "Copy/Move Sheet - To New Document"... Actual Results: SUMIF returns 123, which is the value of row #3 of the original Sheet1. Expected Results: SUMIF should returns 0. Reproducible: Always User Profile Reset: No Additional Info: I find this bug in version 5.2.2.2, and it still exists in version 5.2.3.1. Version: 5.2.3.1 Build ID: 01ec8f357e651ca9656837b783cf7e6a32ee4d92 CPU Threads: 4; OS Version: Linux 4.4; UI Render: default; Locale: zh-CN (zh_CN.UTF-8); Calc: group User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:49.0) Gecko/20100101 Firefox/49.0
Created attachment 128016 [details] test ods file
Reproducible. Win10x64 Version 3.6.7.2 Build ID: e183d5b Version 4.0.6.2 Build ID: 2e2573268451a50806fcd60ae2d9fe01dd0ce24 Version 4.1.6.2 Build ID: 40ff705089295be5be0aae9b15123f687c05b0a Version: 5.3.0.0.alpha0+ Build ID: ed5ca17dce1d088ce3fbbb3a30f748ba92cd07d9 CPU Threads: 4; OS Version: Windows 6.19; UI Render: GL; TinderBox: Win-x86@42, Branch:master, Time: 2016-10-09_05:40:51 Locale: es-ES (es_ES); Calc: CL Looks the issue is about how blank cell are treated for SUMIF criteria, doesn't meet the criteria with data on the same file but is taken as true when data is on a different file. With 3.3 wasn't possible use data in other files for SUMIF.
As the issue it's not really about copy/move sheet but SUMIF with reference to other files, changed the title.
Seems that we have the same problem with AVERAGEIF function.
*** Bug 105414 has been marked as a duplicate of this bug. ***
** 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
Dear Kevin Suo, 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://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
Works for me now. Versión: 6.4.5.2 (x64) Id. de compilación: a726b36747cf2001e06b58ad5db1aa3a9a1872d6 Subprocs. CPU: 4; SO: Windows 10.0 Build 19608; Repres. IU: predet.; VCL: win; Configuración regional: es-ES (es_ES); Idioma de IU: es-ES Calc: threaded