Description: We have source data and an output formula that uses that data. We move the source data to another place by dragging the mouse. The addresses in the resulting formula are modified. We perform the CTRL+Z operation, reverting the changes made. If the resulting formula is in the same sheet as the source data, the operation is performed correctly. If the result formula is on a different worksheet, even though the source data returns to where it was, the addresses in the result formula are not restored. Performing the same operation with CTRL+X → CTRL+V can be undone without any problems (press CTRL+Z twice). Actual Results: Enter the case number A1 of sheet1. Enter the formula =sheet1.A1 in sheet2. Drag cell A1 in sheet1 with the mouse. The address in the formula has changed accordingly. Do CTRL+Z. Expected Results: The formula in cell A1 in sheet2 does not have the original address Reproducible: Always User Profile Reset: No Additional Info: Restore the address from before the change.
Confirmed. Already in 6.2.8, ok in 6.2.0; regression, requesting bibisect.
Bibisected repository win32-6.2. Couldn't find dennis.francis@collabora.com in the mailing list, unsure if dennisfrancis.in@gmail.com belongs to the dev. Regression introduced via: https://git.libreoffice.org/core/+/559dadd0d6eaa61dab7e0bc2a510b87b7109be22 Note that this commit was done to fix Bug 124326: https://bugs.documentfoundation.org/show_bug.cgi?id=124326 2f411ac7514462e199d9730116922069d7447cf8 is the first bad commit commit 2f411ac7514462e199d9730116922069d7447cf8 Author: Norbert Thiebaud <nthiebaud@gmail.com> Date: Sat Apr 6 07:19:33 2019 -0700 source 559dadd0d6eaa61dab7e0bc2a510b87b7109be22 commit 559dadd0d6eaa61dab7e0bc2a510b87b7109be22 [log] author Dennis Francis <dennis.francis@collabora.com> Thu Apr 04 14:07:11 2019 +0530 committer Dennis Francis <dennis.francis@collabora.com> Sat Apr 06 16:05:30 2019 +0200 tree 5ca85a5ee3327170acdfe714dc5a4e3a0f88da3b parent e59e4c41e0fd9beaa03a60def58feefdef1e0bb6 [diff]
Dear Jerzy Moruś, 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
The problem still occurs in version 25.8. The problem does not occur in Apache OpenOffice 4.1.15.