Created attachment 126307 [details] Test file to show missing charts bug with grouped data The attached odb file has a simple embedded HSQLDB database with two groups 'A' & 'B'. 'Line charts report' has Query1 as source, and a line chart in the group footer which uses the same Query1 as source with linked data fields to establish grouping for the charts. When executed, the report shows numeric/text data fields correctly and has space for the charts but no charts are shown. If the linked data fields for the chart are removed/deleted, the charts are shown but with all the data points in each chart (ie not grouped). I understand that this is expected behaviour without linked data fields. A workaround has been found (see bug 100569) whereby the report query is duplicated: one query is used as source for the report and the duplicate query as source for the chart. Then the charts are shown correctly. However, IMHO this is a bug when Report Builder cannot use the same query for text and chart for the same grouped data in the same report. This issue also arises with XY charts.
Could confirm the buggy behavior. Data in a chart couldn't use the same datasource as the report if the charts should show the data of only one group. Linking field from report to data will hide the whole chart. Example, how it must be: https://bugs.documentfoundation.org/attachment.cgi?id=126250 Here the data for the chart are the same, but the datasource is a second query with the same content.
** 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
(In reply to QA Administrators from comment #2) AFAIK, charting in LO Base v6 is comprehensively broken, so I can't test this bug in LO v6. I have tried most releases (from TDF website) since LO v5.3, and have found that charting in LO Base is broken in one way or another in all them. Running a chart report produces a blank space where the chart should be. Clicking on a chart in Report Builder (to edit it or check settings) likely crashes LO Base. So I am sticking with LO v5.3.6.1 in a separate install for Base reporting, which still works for me (well, works well enough). Text reports in LO Base v6 and previous versions work well. Report Builder seems a lot more stable than it was. So the regression with charts is disappointing - and hard to understand as there seems to have been no changes in LO Base functionality (nothing in release notes). I have experimented with scripts to recreate chart reports for each new LO release, because recreating the reports has resolved some issues in the past, but without success for charts. It seems to me that the issues are not in Report Builder itself but with the underlying API. Just to confirm that I am running LO from TDF on OpenSuse 42.3 x64.
Dear branestawm, 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
Bug couldn't be tested, because charts aren't shown since LO 5.4.0.3. See bug 117162
(In reply to Robert Großkopf from comment #5) > Bug couldn't be tested, because charts aren't shown since LO 5.4.0.3. See > bug 117162 Seconded. AFAIK, charting in LO Base v6 is comprehensively broken, so I can't test this bug in LO v6.
Dear branestawm, 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
Seconded (I agree with previous comment).
Bug still reproducible in Version: 7.4.0.0.alpha0+ / LibreOffice Community Build ID: 040b3198fde3385e19e7380fdcabae84a0abac9d CPU threads: 8; OS: Mac OS X 12.2.1; UI render: default; VCL: osx Locale: fr-FR (fr_FR.UTF-8); UI: en-US Calc: threaded
Dear branestawm, 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
(In reply to QA Administrators from comment #11) Bug persists in LO 7.4.3.2 on OpenSUSE LEAP 15.5. In general, LO Base chart reports seem to have improved somewhat in v7 onwards. However, Report Builder remains "flaky": it crashed several times today as I repeated this test with different chart types and colour combinations. So I am staying with my Basic "templates" for chart reports, which call the API directly and reliably. I regret I do not have time to test with the latest LO 7.6+, particularly as running different versions can cause difficulties with Java DB drivers.
Bug still exists on OpenSUSE 15.4 with Version: 24.2.2.2 (X86_64) / LibreOffice Community Build ID: d56cc158d8a96260b836f100ef4b4ef25d6f1a01 CPU threads: 6; OS: Linux 5.14; UI render: default; VCL: kf5 (cairo+xcb) Locale: de-DE (de_DE.UTF-8); UI: de-DE Calc: threaded If I set datasource of the report to another source (here: "Table1") the chart will be shown.