calc 5.0.6.2: data ranges of charts in duplicated sheet point to original sheet rather than to duplicated one. really time-wasting sine it forces user to edit every duplicated data range manually. at times it does do the right thing at times it doesn't. :)
Please attach a test file showing the issue and describe step by step how to reproduce the problem. Please describe precisely how you duplicate the sheet with the chart. Set status to NEEDINFO, please set it back to UNCONFIRMED once requested informations are provided. Best regards. JBF
*** This bug has been marked as a duplicate of bug 43175 ***
Created attachment 132285 [details] Data range of chart is not properly changed when copying a sheet with graphs multiple times
(In reply to snowboard975 from comment #3) > Created attachment 132285 [details] > Data range of chart is not properly changed when copying a sheet with graphs > multiple times (In reply to Jean-Baptiste Faure from comment #1) > Please attach a test file showing the issue and describe step by step how to > reproduce the problem. Please describe precisely how you duplicate the sheet > with the chart. > > Set status to NEEDINFO, please set it back to UNCONFIRMED once requested > informations are provided. > > Best regards. JBF (In reply to Jean-Baptiste Faure from comment #1) > Please attach a test file showing the issue and describe step by step how to > reproduce the problem. Please describe precisely how you duplicate the sheet > with the chart. > > Set status to NEEDINFO, please set it back to UNCONFIRMED once requested > informations are provided. > > Best regards. JBF Reproducible on Windows 7 (64-bit) Version: 5.2.6.2 (x64) Build ID: a3100ed2409ebf1c212f5048fbe377c281438fdc CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; Locale: en-US (nl_BE); Calc: group How to reproduce: 1. Download the attached ods file in comment 3. 2. Copy the second sheet, Blad2, to the left side of the first sheet as its default new name, Blad2_2. 3. Copy the second sheet, Blad1, to the left side of the first sheet as its default new name, Blad1_2. 4. Copy the second sheet, Blad2_2, to the left side of the first sheet as its default new name, Blad2_2_2. 5. Copy the second sheet, Blad1_2, to the left side of the first sheet as its default new name, Blad1_2_2. 6. Click the second sheet, Blad2_2_2, and check the data range of the top left graph. Its expected value is $Blad2_2_2.$A$2:$B$7,$Blad2_2_2.$B$1. However, it points to $Blad2_2.$A$2:$B$7,$Blad2_2.$B$1.
This bug is reproducible as in comment 4. I also received a comment in thread of bug 43175 that this is an independent bug apart from bug 43175. Therefore, I have changed its status back to new.
(In reply to marc from comment #0) > calc 5.0.6.2: data ranges of charts in duplicated sheet point to original > sheet rather than to duplicated one. > > really time-wasting sine it forces user to edit every duplicated data range > manually. > > at times it does do the right thing at times it doesn't. :) I absolutely agrees with marc's comment especially in the following sentence. "really time-wasting sine it forces user to edit every duplicated data range manually. at times it does do the right thing at times it doesn't. :) " It seems there is a workaround. Saving a worksheet immediately after copying a sheet that contains graphs and repeating saving it every time you copy the worksheet seems to prevent this problem. Does it also work for you?
** 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
I can reproduce this according to the instructions of comment 4 (with LO 6.0.7.3 64bit from the Ubuntu repos).
Dear marc, 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
I can reproduce this bug according to the instructions of comment 4, with: Version: 6.4.7.2 Build ID: 1:6.4.7-0ubuntu0.20.04.1 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3; Locale: en-US (en_US.UTF-8); UI-Language: en-US Calc: threaded and the LibreOffice-fresh.basic-x86_64.AppImage: Version: 7.2.0.4 / LibreOffice Community Build ID: 9a9c6381e3f7a62afc1329bd359cc48accb6435b CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded
I cannot reproduce the bug anymore in: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 6c2542306bcc7caaab947664f252265058964fc2 CPU threads: 16; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-US Calc: CL threaded