Description: I have sheet with a column than can change to #N/A to remove lines from certain plots. In an scatter plot if that column is the Y values the line disappears as expected, but if it is the X values, the plot change to a line plot (like the X coordinates are 1, 2, 3...) Notice that if the X values are empty this is not happening. In Excel 2010 and newer this behavior is not happening: In a scatter plot a line with all the X values set to #N/A is not plotted. Steps to Reproduce: 1. Create a scatter plot with the Y set to valid values. 2. Set all the X to NA() Actual Results: The line is then plotted as the X values are 1, 2, 3... Expected Results: The line is not plotted Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: The expected result is the Excel behaviour. Version: 5.4.3.2 (x64) Build ID: 92a7159f7e4af62137622921e809f8546db437e5 CPU threads: 4; OS: Windows 6.1; UI render: default; Locale: en-GB (en_GB); Calc: CL User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.113 Safari/537.36
(In reply to killerrex from comment #0) > Steps to Reproduce: > 1. Create a scatter plot with the Y set to valid values. > 2. Set all the X to NA() Please attach an example document. Set to NEEDINFO. Change back to UNCONFIRMED after you have provided the document.
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping-20180703
Created attachment 143478 [details] Working Excel version Excel sheet that works as expected. Setting the cell C2 a value: + -10 or lower the plot is empty + +10 or bigger the plot is an horizontal parabola + For intermediate values only part of the parabola is shown.
Created attachment 143481 [details] Non working Calc workbook Libreoffice version that does not work as expected. Setting the cell C2 a value: + -10 or lower the plot is *NOT* empty as expected, but the values of Y are plot. + +10 or bigger the plot is an horizontal parabola + For intermediate values only part of the parabola is shown. The bad behaviour happens both in Windows 7 with Libreoffice 6.0.5 and Linux Opensuse Tumbleweed and Libreoffice Versión: 6.1.0.0.beta2+ Compilation 10(Build:0)
I added 2 versions of the same simple Excel sheet that reproduce the bug. In both cases playing with the cell C2 is possible to see the bug: - For values over -9 the X values is mix between N/A and numbers, so the horizontal parabola is plot (or part of it) - For values of -10 or lower, all the X values are N/A. In Excel the line disappears (the plot is empty). In Libreoffice the plot changes to "Line mode" and plots the Y values in function of the index.
Ok, looks like it behaves the same way in 3.3.0 Arch Linux 64-bit Version: 6.2.0.0.alpha0+ Build ID: bd394492c165d27c96a44495d9ca694a242acb8f CPU threads: 8; OS: Linux 4.17; UI render: default; VCL: gtk3; Locale: fi-FI (fi_FI.UTF-8); Calc: group threaded Built on July 11th 2018 Arch Linux 64-bit LibreOffice 3.3.0 OOO330m19 (Build:6) tag libreoffice-3.3.0.4
Dear killerrex, 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
Dear killerrex, 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
Created attachment 174018 [details] Example created with v7.1.5.2 I confirm is still present in linux latest Libreoffice stable version: Version: 7.1.5.2 / LibreOffice Community Build ID: 10(Build:2) CPU threads: 8; OS: Linux 5.13; UI render: default; VCL: gtk3 Locale: es-ES (es_ES.utf8); UI: es-ES Gentoo official package Calc: threaded I add a new example, created with this version of LibreOffice.
Dear killerrex, 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