Created attachment 93373 [details] Original excel spreadsheet with explicit data ranges One of the features I use a lot in Excel is to create a data series explicitly from a {value list} instead of off the cells in the spreadsheet. I use it to draw lines on the chart for engineering limits, but there will be other reasons for doing it. Calc does not support these explicit data series at all.
Created attachment 93374 [details] Screen grab of the excel file and chart
Created attachment 93375 [details] Screen grab of the excel data range dialogue showing how the horizontal line was produced
Created attachment 93376 [details] Screen grab of the excel data range dialogue showing how the vertical line was produced
Created attachment 93377 [details] Screen grab of the .xls file opened in calc. Not the same.
Created attachment 93378 [details] Screen grab of the excel data range dialogue showing how the horizontal line was produced - correct file uploaded!
Created attachment 93379 [details] Screen grab of the horizontal data line range as displayed in calc
Created attachment 93380 [details] Screen grab of the vertical data line range as displayed in calc
Created attachment 93381 [details] Data file after being opened in calc and saved as default format
Created attachment 93382 [details] Data file after being opened in calc and saved in .xls format
Created attachment 93383 [details] Screen grab once opened in calc and re-saved as .xls, then re-opened in excel
Created attachment 93384 [details] Screen grab once opened in calc and re-saved as .xls then re-opened in excel - the explicit data ranges have gone
This is a compatability issue with excel. As the attachments show, opening a known good .xls produces a different graph in calc, and if re-saved as an .xls from calc the explict data ranges are gone when reverting to excel. It is also something of a shame that the rather convenient feature that allows me to draw on a graph without creating dummy data series is not available in calc.
Created attachment 108633 [details] PDF saved from Excel 2010 PDF showing, how it should look like.
I confirm that Calc still doesn't show it like it's supposed to. Win 7 64-bit Version: 4.4.0.0.alpha1+ Build ID: 4586a3f564600f1a0ce15a5cb98868b43bb9351e TinderBox: Win-x86@42, Branch:master, Time: 2014-10-29_07:28:16
Lowered version number after reproducing with: Ubuntu 14.10 64-bit 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 on a currently supported version of LibreOffice (5.0.4 or later) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2016-01-17
I can confirm that this bug is still present in 5.0.4.2
I can confirm as requested that this bug was carried over from OOo (and is still present in OOo 4.1.2)
** 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 on a currently supported version of LibreOffice (5.2.5 or 5.3.0 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170306
I can confirm that this behaviour is unchanged in 5.3, and is unchanged
** 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
Tested in 6.0.2.1 and still present Version: 6.0.2.1 (x64) Build ID: f7f06a8f319e4b62f9bc5095aa112a65d2f3ac89 CPU threads: 8; OS: Windows 10.0; UI render: GL; Locale: en-GB (en_GB); Calc: group
Bug still present in 6.2.1.2 installed yesterday
I think your robot has gone wrong. I just answered this when it appeared as comment 23, and it is back as comment 25 a day later. No, it has NOT been fixed yet.
(In reply to Bob Harvey from comment #26) > I think your robot has gone wrong. > I just answered this when it appeared as comment 23, and it is back as > comment 25 a day later. > No, it has NOT been fixed yet. I have reported the misbehaving robot to the authorities.
Created attachment 161940 [details] Screen grab opened in Version 7.0.0.0 beta1 I thought I would try this in the V7 beta. The bug is still present in that one.
Dear Bob Harvey, 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
With apologies, I had not seen the challenge in 2022. Yes, this bug still exists. I have just tried it in 7.5.2.2
Created attachment 186701 [details] Screen grap opened in 7,5,2,2