Bug 44626 - Copying a XY (scatter) chart with first row as label leads to incoherent data range
Summary: Copying a XY (scatter) chart with first row as label leads to incoherent data...
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Chart (show other bugs)
(earliest affected)
3.4.4 release
Hardware: All Windows (All)
: high normal
Assignee: Not Assigned
Depends on:
Blocks: Chart-Data
  Show dependency treegraph
Reported: 2012-01-10 03:31 UTC by daniel.schaaaf
Modified: 2020-09-18 20:15 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description daniel.schaaaf 2012-01-10 03:31:15 UTC
1) Open Calc, mark cells A1:B2 and insert a XY (scatter) chart with "data series in columns" and "first row as label"
=> data range is: $Sheet1.$A$1:$B$2

2) Make a copy of that chart
=> data range is: $Sheet1.$A$2:$B$2,$Sheet1.$B$1

This renders creating multiple charts with the same layout but different data very difficult. After one has copied a chart and adjusted the data range one always has to change the first (label) row back to the original. In the above example I would change $Sheet1.$A$2:$B$2 to $Sheet1.$A$3:$B$3 and then would have to revert $Sheet1.$B$1 back to $Sheet1.$A$1:$B$1 or my freshly copied chart would become corrupted.

I noticed that LibreOffice sometimes recognizes a corrupted data range and fixes it, but when the data range is more complex than in the above example then data ranges get seriously corrupted and charts turn to garbage.
Comment 1 ign_christian 2013-05-23 15:21:22 UTC
reproducible on LO (Win7 32bit)

weird behavior..seems that data ranges on XY chart not remembered properly
Comment 2 QA Administrators 2016-01-17 20:02:28 UTC Comment hidden (obsolete)
Comment 3 daniel.schaaaf 2016-01-17 20:47:30 UTC
Bug reproducible in v5.0.4.2 and no changes in bug behaviour.

Tested on Windows Server 2012 R2.
Comment 4 QA Administrators 2017-03-06 13:55:45 UTC Comment hidden (obsolete)
Comment 5 daniel.schaaaf 2017-03-06 17:13:29 UTC
Bug still present in (x64) on Windows 10 Pro.
Comment 6 QA Administrators 2018-06-15 02:45:28 UTC Comment hidden (obsolete)
Comment 7 QA Administrators 2020-06-15 03:40:05 UTC Comment hidden (obsolete)
Comment 8 andis.lazdins 2020-06-15 05:52:20 UTC
Reproducible in, solved in
Comment 9 Goyo 2020-09-18 19:57:26 UTC
Works for me in LO 7.0.1.