Bug 155409 - Chart for different data series: no separate data labels
Summary: Chart for different data series: no separate data labels
Status: RESOLVED DUPLICATE of bug 38760
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
7.5.3.2 release
Hardware: All All
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-05-19 14:07 UTC by goodguy00@zoho.com
Modified: 2023-05-23 13:05 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
chart with 2 series (29.32 KB, application/vnd.oasis.opendocument.spreadsheet)
2023-05-19 14:07 UTC, goodguy00@zoho.com
Details
result chart (80.77 KB, image/png)
2023-05-23 09:46 UTC, goodguy00@zoho.com
Details

Note You need to log in before you can comment on or make changes to this bug.
Description goodguy00@zoho.com 2023-05-19 14:07:31 UTC
Created attachment 187400 [details]
chart with 2 series

attached spreadsheet: 2 data series in one chart. the 2 data series obviously have different dataranges. both are called "column E" and i did not find a way how to change their name. no problem, just ugly.
=> even though the data ranges are different, it is not possible to change the data labels for each data series separately. if having the labels for all data series the same is intentional, i doubt it is useful.
Comment 1 Jaske Sk 2023-05-19 15:50:03 UTC Comment hidden (spam)
Comment 2 m_a_riosv 2023-05-19 21:32:08 UTC
Reproducible.
Version: 7.5.3.2 (X86_64) / LibreOffice Community
Build ID: 9f56dff12ba03b9acd7730a5a481eea045e468f3
CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win
Locale: es-ES (es_ES); UI: en-US Calc: CL threaded
Version: 7.6.0.0.alpha1+ (X86_64) / LibreOffice Community
Build ID: b3c88dc039d447322b8c8c564ab6e2f0ce9c5b90
CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win
Locale: es-ES (es_ES); UI: en-US Calc: CL threaded
Comment 3 Stéphane Guillou (stragu) 2023-05-22 14:57:32 UTC
In general, data series labels are:
- the name of the Column if no label in the range
- the label of the series if range contains a label ("First column as label" option in the "Data range" tab)

If a label is present, the "Range for Name" field contains the reference to that cell.

I'm not sure how the chart was created, but in your example file, both series have "$Timeline.$A$1" as the range for name, which is empty. It therefore defaults to "Column E", which is where the data is for both series.

In my opinion, this is not a bug. The default label is used, and can be changed if needed (by adapting the range so it does include the labels in rows 29 and 68, or by manually changing the Range for Name values to $Timeline.$E$29 and $Timeline.$E$68 respectively).

Tested with:

Version: 7.6.0.0.alpha1+ (X86_64) / LibreOffice Community
Build ID: f4c24da1e7f11664e0d2f688d2531f068e4a3bc0
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded
Comment 4 goodguy00@zoho.com 2023-05-23 09:35:32 UTC
i do not agree. true, the "Range for Name" contains garbage in my example, but does not make any difference for my point. it seems to reflect only the name of the data series in the "data ranges" popup and i did not care for that.
if you remove the value in the "data labels" field, you end up with numbers as identifiers of the data in the chart, irrelevant what the "Range for Name" says.
the problem of the data point naming could be easily solved, if only the "data labels" would belong to the various data series, instead of being global and only once for all of them.
Comment 5 goodguy00@zoho.com 2023-05-23 09:46:06 UTC
Created attachment 187453 [details]
result chart

this is what i'm trying to achieve. each series needs to have its own labels.
Comment 6 Stéphane Guillou (stragu) 2023-05-23 13:05:02 UTC
Right, apologies, I misunderstood your issue.
I understand better now, I can see that the two data label ranges are synced between the two series.

This is already reported in bug 38760, so I am marking as a duplicate.
Please chime in there if you want, I will mention your example document as I think it is a good illustration of the problem.

Thank you!

*** This bug has been marked as a duplicate of bug 38760 ***