Description: When a whole column is cut from a spreadsheet and pasted into a different column with the other cells shifted to the right, formulas that are located right from the original location of the cut column break. This bug needs specific circumstances to occur: - The cells should be referenced without a function, so the bug only occurs when the cells are referenced like =A1+B1+C1, but not when they are referenced like =SUM(A1:C1); - The bug doesn't occur either if a new column is inserted to the intended location manually with the Insert Columns Left command and the content is inserted into this newly created column; - Another way to avoid the bug is to insert a new column to the intended location manually with the Insert Columns Left command, then Undo it with Ctrl+Z, and then insert the content with Paste Special – Shift Cells: Right. Steps to Reproduce: 1. Add a number to the A1 cell 2. Add a number to the B1 cell 3. Add a formula to the C1 cell that references the A1 and B1 cells (e.g.: =A1*B1) 4. Type in some text in the D1 cell 5. Reference the A1, B1 and C1 cells from the E1 cell (e.g.: =A1+B1+C1) 6. Click to the top of the D column to select the whole column and press Ctrl+X 7. Click on the B column and press Ctrl+Shift+V 8. In the Paste Special window select “Paste all” at Selection, and “Right” at Shift Cells, then press OK. Actual Results: In the E1 cell the reference pointing to the B1 cell doesn't get updated to C1 breaking the formula. Expected Results: The reference in the E1 cell should be updated to the new location. Reproducible: Always User Profile Reset: No Additional Info:
Created attachment 146653 [details] The file to reproduce the issue. [it's not, it just is a copy of the bug description as text .odt file]
Created attachment 146654 [details] A screenshot showcasing the issue.
Reproduced in Version: 6.2.0.0.alpha1+ Build ID: db01b26d2e7d6626b7504fc7ee6ba6aac50e6098 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); UI-Language: en-US Calc: threaded Version: 5.2.0.0.alpha0+ Build ID: 3ca42d8d51174010d5e8a32b96e9b4c0b3730a53 Threads 4; Ver: 4.10; Render: default; Version: 4.3.0.0.alpha1+ Build ID: c15927f20d4727c3b8de68497b6949e72f9e6e9e Version 4.1.0.0.alpha0+ (Build ID: efca6f15609322f62a35619619a6d5fe5c9bd5a)
@Eike, I thought you could be interested in this issue...
Created attachment 146680 [details] The file to reproduce the issue.
Dear NISZ LibreOffice Team, 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
reproducible with: Version: 6.3.3.2 (x64) Build-ID: a64200df03143b798afd1ec74a12ab50359878ed CPU-Threads: 4; BS: Windows 10.0; UI-Render: Standard; VCL: win; Gebietsschema: de-DE (de_DE); UI-Sprache: de-DE Calc: Version: 6.5.0.0.alpha0+ (x64) Build ID: d04eef858250f97690f32dba17f42d157a8767fc CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: default; VCL: win; Locale: de-DE (de_DE); UI-Language: en-US Calc: threaded Formula in E1 (-> F1 after shifting right) points to: =A1+C1+B1 and results to #VALUE
Dear NISZ LibreOffice Team, 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
reproduce It seems that when the cell address in the formula is shifted to the cell address where the cut was made, it is corrected to the cell address where the paste was made. https://ask.libreoffice.org/t/topic/106010/9 copy+pastespacial(shift) not repro alt+drag not repro Version: 24.8.0.0.alpha1 (X86_64) / LibreOffice Community Build ID: a17e39caaf73108bee692d6f64a44c62f4066f1d CPU threads: 12; OS: Windows 11 X86_64 (10.0 build 22631); UI render: Skia/Raster; VCL: win Locale: ja-JP (ja_JP); UI: ja-JP Calc: CL threaded
There is no consistency in following absolute references Shifting rows or columns may or may not change the references as expected. For more information, see the Japanese Ask. https://ask.libreoffice.org/t/topic/106010
Reproduced in Version: 24.2.3.2 (X86_64) / LibreOffice Community Build ID: 433d9c2ded56988e8a90e6b2e771ee4e6a5ab2ba CPU threads: 4; OS: Linux 5.10; UI render: default; VCL: gtk3 Locale: ja-JP (ja_JP.UTF-8); UI: ja-JP Calc: threaded The case discussed in Japanese ASK used absolute references, so the situation may be a little different, but there were problems even with absolute references.