Description: When an X-Y scatter chart has a linear trendline, the trendline will become a mean value line, if the X values are formatted as a dates AND the trendline has 'force intercept' selected. Also, the intercept value has a maximum entry of 10,000, which is much too low. Steps to Reproduce: 1. create an x-y scatter chart with data as numbers 2. add a linear trendline 3. format the x values as 'date' and set them as valid dates 4. set 'force intercept' on the trendline with an appropriate value Actual Results: Trendline on chart becomes a horizontal mean value line, while still displaying as a trendline. Expected Results: Trendline should adjust to have y intercept as selected Reproducible: Always User Profile Reset: No Additional Info: Version: 7.0.5.2 (x64) Build ID: 64390860c6cd0aca4beafafcfd84613dd9dfb63a CPU threads: 8; OS: Windows 10.0 Build 19041; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL
(In reply to elittera from comment #0) > Description: > When an X-Y scatter chart has a linear trendline, the trendline will become > a mean value line, if the X values are formatted as a dates AND the > trendline has 'force intercept' selected. Also, the intercept value has a > maximum entry of 10,000, which is much too low. > > Steps to Reproduce: > 1. create an x-y scatter chart with data as numbers > 2. add a linear trendline > 3. format the x values as 'date' and set them as valid dates Please attach an example document showing the state at step 3 so we can quickly test. Set to NEEDINFO. Change back to UNCONFIRMED after you have provided the document.
Seems duplicate by title. Sample would still be useful. *** This bug has been marked as a duplicate of bug 140555 ***
Reproduce in 7.1 and 7.4+. Linear is not really replaced by Mean but looks so.
Created attachment 180726 [details] Test ODS
Dear elittera, 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