Bug 101966 - Label corruption in diagram after cells translation
Summary: Label corruption in diagram after cells translation
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
5.2.0.4 release
Hardware: x86-64 (AMD64) Linux (All)
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Chart
  Show dependency treegraph
 
Reported: 2016-09-07 14:30 UTC by Dimitri Bouron
Modified: 2023-05-27 07:38 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Result of described steps (12.38 KB, application/vnd.oasis.opendocument.spreadsheet)
2016-09-07 14:30 UTC, Dimitri Bouron
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Dimitri Bouron 2016-09-07 14:30:24 UTC
Created attachment 127196 [details]
Result of described steps

1) Open Calc, fill A1:B1 with labels and add some data to A2:B3.

2) Create diagram by selecting a larger area than previous filled. For example: A1:D10.
You should have some extra label for every empty column (By default: "Column <column_letter>") and empty rows.


3) Select filled cells, A1:B3, and shift them to B1:C3 (One column on the right). Labels and data will be copied correctly on calc sheet.
But on diagram, labels now points on real column position + number of shifted column.
Except for original empty column.

Bug seems to appear with any diagram type.
Same behaviour with cut/past.

Reproducible on LO 5.2.0.4 and on 5.3.0.0 alpha+ Master (Both on Fedora 24).
Comment 1 Buovjaga 2016-09-29 19:25:49 UTC
Repro.

Tested in old version, 3.6, but it works differently: it ignores the empty cells when creating the chart.

Arch Linux 64-bit, KDE Plasma 5
Version: 5.3.0.0.alpha0+
Build ID: 7cf444454c0c27e2f6d764164ea880b87163f45a
CPU Threads: 8; OS Version: Linux 4.7; UI Render: default; 
Locale: fi-FI (fi_FI.UTF-8); Calc: group
Built on September 27th 2016
Comment 2 QA Administrators 2017-10-23 14:03:10 UTC Comment hidden (obsolete)
Comment 3 QA Administrators 2019-12-03 13:52:31 UTC Comment hidden (obsolete)
Comment 4 QA Administrators 2021-12-03 04:20:59 UTC
Dear Dimitri Bouron,

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