Created attachment 75197 [details] Example of non-contiguous calc chart category bug This bug appears to be similar to 53300, but doesn't seem to match exactly. Sorry if it does turn out to be a duplicate. When working with non-contiguous data ranges, I am able to get the proper behavior for the actual data for a chart, but not for the category labels. It seems to concatenate the second range with each item in the first range and then associate that value with only the items in the first data range. I'm having a rather difficult time describing the bug, so I've included an example spreadsheet. I am using commas to separate the compound ranges such as A2:A13,C2:C13. I did experience difficulties with defining the non-contiguous charts when using the create chart wizard. I had to manually modify the data ranges after it was created. But I guess that part has more to do with bug 53300. I'm not sure when this bug showed up, but I know this behavior worked correctly back in OpenOffice 3.2.1. I am currently experiencing this bug using LibreOffice 3.6.5.2 from the main Arch Linux repo.
Created attachment 75584 [details] Screenshot of chart category bug I've added a screenshot of the bug using LibreOffice 3.6.5.2. As you can see, the same syntax is used in both the Y-Values field and the Categories field. The Y-Values are accepted and add data points to the chart. Each item in the second range of categories is just appended to the each item in the first set of categories.
Created attachment 75585 [details] Screenshot of correct (previous) behavior for chart categories Here is a screenshot of the same document loaded in OpenOffice 3.2.1 for an example of how it should behave.
I can confirm reproducible on LO 4.0.4.1 (Win7 32bit) In my opinion Bug 53300, also Bug 55697 is about selecting data beyond existing that is previously impossible. At present it's possible but wrong result.
I can confirm this is still present in 4.1.2.3 Sad to see it is such a long-standing regression!
This is still a valid bug in recent nightly versions. There have been many changes since the last comment, but this bug's behavior is still broken in the same way as originally reported. Version tested: Version: 4.5.0.0.alpha0+ Build ID: 09a1e4f36128f64029d45a38d9b059bf11ea0821 TinderBox: Linux-rpm_deb-x86@45-TDF, Branch:master, Time: 2015-04-15_23:40:36 Locale: en_US
same problem in version 4.2.8.2 and catagory-problems also for donut charts for 2. or more rings with non-contiguous data ranges
same problem in version 5.1.2.2 and catagory-problems also for donut charts for 2. or more rings with non-contiguous data ranges
** 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.7 or 5.3.3 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-20170522
This bug is still present in 5.3.3.
Changing version back to the earliest affected version.
** 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 same bug with the following versions/config: Version: 5.4.6.2 Build ID: 4014ce260a04f1026ba855d3b8d91541c224eab8 CPU threads: 2; OS: Linux 3.13; UI render: default; VCL: kde4; Locale: en-GB (en_GB.UTF-8); Calc: group Version: 6.1.0.0.beta1 Build ID: 8c76dfe1284e211954c30f219b3a38dcdd82f8a0 CPU threads: 2; OS: Linux 3.13; UI render: default; VCL: kde4; Locale: en-GB (en_GB.UTF-8); Calc: group
Dear tmacalp, 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
Can reproduce with: Version: 6.3.0.0.beta1 Build ID: a187af327633f5f00363be5131bd21a13e0f1a7b CPU threads: 8; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: en-AU (en_AU.UTF-8); UI-Language: en-US Calc: threaded .. and: Version: 6.2.4.2 Build ID: 1:6.2.4-0ubuntu0.18.04.1~lo1 CPU threads: 8; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: en-AU (en_AU.UTF-8); UI-Language: en-GB Calc: threaded
still bug in 7.1 from 2020-09-05 win7x64, already bug in 3.5.1.2 win7x64, issue looks - besides some parts of the range definitions containing small errors - depending on both 'parts' of the data area starting in the same row, move e.g. C2:D13 to C3:D14 (select and ctrl-x ctrl-v), then chart display will be correct, at least improved ... may be that helps in debugging ... old bug, and regression as old sample looks better,
Dear tmacalp, 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
Bug still present in: Version: 7.5.0.0.alpha0+ / LibreOffice Community Build ID: 3752e8eaa81a50b018669d03dc59b3753a5248ef CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded
Can confirm that this 9 year old bug still exists...