Download it now!
Bug 58244 - Impossible to display non numeric values (labels) in bubble charts axis (for categorized data)
Summary: Impossible to display non numeric values (labels) in bubble charts axis (for ...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Chart (show other bugs)
Version:
(earliest affected)
3.6.2.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Chart-Labels
  Show dependency treegraph
 
Reported: 2012-12-13 14:36 UTC by Antonello
Modified: 2019-10-31 10:52 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Example data showing no string labels are possible on bubble chart axis (27.88 KB, application/vnd.oasis.opendocument.spreadsheet)
2012-12-13 14:36 UTC, Antonello
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Antonello 2012-12-13 14:36:10 UTC
Created attachment 71448 [details]
Example data showing no string labels are possible on bubble chart axis

Bubble charts allows to display data having 3 dimensions, where the first two are used to place the bubble in a X,Y grid and the third one to size the bubble itself.

However it works only when X and Y are numerical values, while it doesn't work instead when they are strings (useful for categorized data, where the X and Y dimensions are categories rather than continuous values).
This is an odd behaviour as most other type of charts are able to place strings on their axis.

Here is an example of what I'd like to achieve: http://static.ipaditalia.com/wp-content/uploads/2012/10/google_tablet_research_locations.jpg

I attach some example data.

Thank you ;-)
Comment 1 Buovjaga 2014-11-07 14:43:10 UTC
Confirmed.

Win 7 64-bit Version: 4.4.0.0.alpha1+
Build ID: 8b21b5cbe78945b27525b4ce78ae3d981f90590f
TinderBox: Win-x86@39, Branch:master, Time: 2014-11-06_03:55:51
Comment 2 Dietmar 2015-10-23 13:49:04 UTC
I can confirm this with LOo Version: 5.0.2.2 (x64)
Build-ID: 37b43f919e4de5eeaca9b9755ed688758a8251fe
Gebietsschema: de-DE (de_DE).

If I have names in the first column and select the column as label for axis, just numbers shown on axis.

Dietmar
Comment 3 QA Administrators 2016-11-08 11:24:37 UTC Comment hidden (obsolete)
Comment 4 Antonello 2016-11-08 11:40:10 UTC
Bug still present as LibreOffice 5.2.2.2 (Linux 64 bit in my case, but OS independent)
Comment 5 QA Administrators 2017-11-09 07:43:20 UTC Comment hidden (obsolete)
Comment 6 Antonello 2017-11-09 10:34:15 UTC Comment hidden (obsolete)
Comment 7 Buovjaga 2017-11-09 15:59:08 UTC
(In reply to Antonello from comment #6)
> 1-year is too a short timeframe. I still have the same version of
> LibreOffice as before on my Ubuntu box, testing the bug for newer LO version
> would require to install non-standard packages.
> Please make this request every 5 years, anyhow 99% the bug is still there.

Nope, we consistently get about 25% of the bugs as "silently fixed".

A quick way to test on Linux without installing anything is AppImage packages: http://libreoffice.soluzioniopen.com/
Comment 8 Antonello 2017-11-09 16:12:26 UTC
Bug still present:
Version: 6.0.0.0.alpha0+
Build ID: cfbb8b5090537e79ba70e250ddee86d53facbe15
CPU threads: 8; OS: Linux 4.10; UI render: default; VCL: gtk2; 
TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2017-10-18_22:54:20
Locale: en-GB (en_GB.UTF-8); Calc: group
Comment 9 QA Administrators 2019-10-31 03:36:06 UTC Comment hidden (obsolete)
Comment 10 Antonello 2019-10-31 10:37:03 UTC
Bug still present Version: 6.3.2.2

@Buovjaga: I am strongly suspecting the 25% "silently fixed" bugs are those where.. the reporter remains "silent" :-|
Comment 11 Buovjaga 2019-10-31 10:52:38 UTC
(In reply to Antonello from comment #10)
> Bug still present Version: 6.3.2.2
> 
> @Buovjaga: I am strongly suspecting the 25% "silently fixed" bugs are those
> where.. the reporter remains "silent" :-|

You did not understand: I was referring to the rate of reports that can be verifiably closed as WORKSFORME. This was observed when methodically going through mass-pinged report batches in the past, retesting everything. It has nothing to do with a reporter NOT testing the bug.