If a formula is entered into a cell that has been merged with adjacent cells and that cell is then copied and pasted (special) into another group of merged cells with only the formula specified then the merged target cells are split. They then need to be manually merged again. This happens if only one group of merged cells are copied from/to or if an entire row is copied. If the formatting is copied as well then the format from the source is properly applied to the target, which in the present case, is not desired. This happens on Linux as well as the Microsoft versions of LO.
Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided. (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.)
Created attachment 131543 [details] Example of merged cells split by formula paste This a simple ods with merged cells in three columns. The centre cell at row ten column 2 had the formula from cell row 2, column 2 copied and then the formula only pasted into it. Th result is that the formerly meged cells at that location are now split.
Created attachment 131801 [details] gdb trace of formula paste splitting merged cells The request trace from LibreOffice-5.3 is attached. Installed Packages Name : libreoffice5.3 Arch : x86_64 Version : 5.3.0.3 Release : 3 Size : 4.3 M Repo : installed From repo : /libreoffice5.3-5.3.0.3-3.x86_64 Summary : Brand module for LibreOffice 5.3 .0.3 License : LGPL Description : Brand module for LibreOffice 5.3
Confirmed in Version: 5.4.0.0.alpha0+ Build ID: 5f33745c1d6750126e53a02b2a95355a3e5b16a0 CPU Threads: 4; OS Version: Linux 4.8; UI Render: default; VCL: gtk2; Locale: ca-ES (ca_ES.UTF-8); Calc: group Steps to reproduce: 1. Open attach document 2. Merge 3 columns in E:22 to H:22 3. Copy E4 4. Paste special in E:22 Result: Merged cells get split.
Regression introduced by: author Tsutomu Uchino <hanya@apache.org> 2014-01-23 11:28:01 (GMT) committer Caolán McNamara <caolanm@redhat.com> 2014-01-23 16:02:10 (GMT) commit 65464fdf04cdadc602d53ef7fda81f0f0647ad46 (patch) tree 04ef29fede3cb638f918544255d9ba37d083bf2d parent ebf5e613a5bea74d6e9801224ab5c29a64b9b11c (diff) Resolves: #i123626# change default for paste special dialog of Calc... to Text, Numbers and Date and time
Ok, so looking at the commit, this is not a bug. it's just that when you use the Special copy, format option is not enabled, if you enable it, then the cells aren't split. Closing as RESOLVED NOTABUG
You have not read the initial report. The only thing being copied and pasted in IS formula. I can assure you that the formula box is checked when this happens and that nothing else is.
In any case, why would copying and pasting text and numbers without format split merged cells in the target as an expected behaviour?
Clarified steps to reproduce: 1. Open attachment 131543 [details] 2. Merge the cells E22 to H22 3. Copy E4 4. Paste special in E22, only tick the Formulas checkbox Result: Merged cells get split. Not related to the commit mentioned in comment 5 as this already happens in 3.5. Win 7 Pro 64-bit Version: 5.4.0.0.alpha0+ Build ID: 1670cc25bc2771e87f7956a4b0dd634abaa4128b CPU threads: 4; OS: Windows 6.1; UI render: default; TinderBox: Win-x86@42, Branch:master, Time: 2017-03-22_23:28:42 Locale: fi-FI (fi_FI); Calc: CL LibreOffice 3.5.0rc3 Build ID: 7e68ba2-a744ebf-1f241b7-c506db1-7d53735
** 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
Repro 6.3+.
Dear James B. Byrne, 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
Bug is still present in 7.0.3.1 on FreeBSD
As far as I understand the LibreOffice source code, i.e. the data model: merging of cells is part of the cell format (style). So, if you do not paste the format, you loose your merge cell information. In this logic, the current behavior is correct. So, I agree with Xisco Fauli with Closing as RESOLVED NOTABUG in comment 6.
(In reply to Scito from comment #14) > As far as I understand the LibreOffice source code, i.e. the data model: > merging of cells is part of the cell format (style). So, if you do not paste > the format, you loose your merge cell information. > > In this logic, the current behavior is correct. > > So, I agree with Xisco Fauli with Closing as RESOLVED NOTABUG in comment 6. But if you do Paste Special - Unformatted text, there is no destruction of the merged format. So why should Paste Special - Values only destroy it?
(In reply to Buovjaga from comment #15) > But if you do Paste Special - Unformatted text, there is no destruction of > the merged format. So why should Paste Special - Values only destroy it? I misunderstood. Yeah, you are right. This is unexpected.
Dear James B. Byrne, 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
Version: 7.4.4.2 / LibreOffice Community Build ID: 40(Build:2) CPU threads: 16; OS: FreeBSD 12.4; UI render: default; VCL: qt5 (cairo+xcb) Locale: en-CA (C); UI: en-US Calc: threaded