Bug 142968 - FILEOPEN DOCX Combo Chart axis label moved to the other axis
Summary: FILEOPEN DOCX Combo Chart axis label moved to the other axis
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.2.0.0.alpha0+
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisected, bisected, regression
Depends on:
Blocks: OOXML-ComboChart
  Show dependency treegraph
 
Reported: 2021-06-21 14:01 UTC by NISZ LibreOffice Team
Modified: 2023-12-18 03:12 UTC (History)
5 users (show)

See Also:
Crash report or crash signature:


Attachments
Screenshot of the original document side by side in Word and Writer (147.99 KB, image/png)
2021-06-21 14:01 UTC, NISZ LibreOffice Team
Details

Note You need to log in before you can comment on or make changes to this bug.
Description NISZ LibreOffice Team 2021-06-21 14:01:17 UTC
Created attachment 173054 [details]
Screenshot of the original document side by side in Word and Writer

Attachment 154208 [details] has an axis label on the primary Y axis in Word, which moved to the secondary in Writer.

Steps to reproduce:
    1. Open attachment 154208 [details]
    2. Observe the combo chart on page 4

Actual results:
The axis label “Aaw Aaatiai ($m)” is attached to the secondary Y axis.


Expected results:
Should be attached to the primary Y axis.

LibreOffice details:
Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: 2a7e64da7f385de8dbba1802530e251cf29259fb
CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: default; VCL: win
Locale: en-US (hu_HU); UI: en-US
Calc: CL

Was good in 7.1

Additional Information:
Bibisected using bibisect-win64-7.2 to:
URL: https://cgit.freedesktop.org/libreoffice/core/commit/?id=be82f6313f298c13a2f040b218c6f2a33705ff8c 

author	Szymon Kłos <szymon.klos@collabora.com>	2021-04-08 15:08:38 +0200
committer	Szymon Kłos <szymon.klos@collabora.com>	2021-04-12 13:39:57 +0200

tdf#140489 fix chart display in xlsx

Adding CC to: Szymon Kłos
Comment 1 Aron Budea 2021-06-22 01:43:39 UTC
Confirmed with LO Version: 7.3.0.0.alpha0+ (51754ca5349d7bf655d57ded37381188d0bc4bcf) / Ubuntu.
Comment 2 QA Administrators 2023-12-18 03:12:10 UTC
Dear NISZ LibreOffice Team,

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