Bug 97802 - Chart categories : manually set strings (not references to table) are displayed as 1 2 3 ...
Summary: Chart categories : manually set strings (not references to table) are display...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Chart (show other bugs)
(earliest affected)
Hardware: All All
: medium minor
Assignee: Not Assigned
Depends on:
Blocks: Chart-Wizard
  Show dependency treegraph
Reported: 2016-02-12 15:22 UTC by Serg
Modified: 2022-01-29 03:54 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:
Regression By:

Invalid category names (888.29 KB, image/png)
2016-02-12 15:22 UTC, Serg

Note You need to log in before you can comment on or make changes to this bug.
Description Serg 2016-02-12 15:22:13 UTC
Created attachment 122581 [details]
Invalid category names

1) Create new table, e g with data:
1	4	2
2	3	1
3	2	2
4	1	1

2) select this range 

3) add column chart 

4) Right-click on X-Axis -> select "Data Ranges..."

5) Change categories to: "Caaaa1","C2","C3"

6) Click OK

7) It's still "1 2 3" in categories names.

Moreover, if you try to load proper XLSX with manually set category names - the resut will be the same - "1 2 3 ..."
Comment 1 Buovjaga 2016-02-16 11:03:05 UTC
Yes, it doesn't change the X axis labels.
The correct form least for me is: "Caaaa1";"C2";"C3" so semicolons instead of commas. Otherwise the background of the input field was red. But it doesn't work..

I tried in 3.5, but there the background of the input field was red with commas or semicolons and it would not accept the categories.

Serg: set the version to the earliest you saw the problem in.

Win 7 Pro 64-bit Version:
Build ID: a6f876d45bd4e41a7143594a6cb11b6893a0f620
CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; 
TinderBox: Win-x86@39, Branch:master, Time: 2016-02-11_00:07:38
Locale: fi-FI (fi_FI)
Comment 2 QA Administrators 2017-03-06 15:24:16 UTC Comment hidden (obsolete)
Comment 3 QA Administrators 2019-12-03 14:57:07 UTC Comment hidden (obsolete)
Comment 4 QA Administrators 2022-01-29 03:54:52 UTC
Dear Serg,

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