Created attachment 151992 [details] data for testing A secondary axis is usually assumed to show different categories or scales and to have data aligned to it. In Chart, it is possible to display a secondary X-axis. However, it does not appear possible for it to have a different scale or to align data to it. There is no indication in the program that it does not work and documentation assumes that it works as expected. To reproduce: 1. Select data (sample data attached) 2. Go to Insert > Chart to open Chart Wizard 3. Click finish to close Chart Wizard 4. In edit mode, go to Insert > Axes 5. In the Axes dialog, click to select Secondary X-Axis What is expected: If data cannot be aligned to the secondary X-axis, I would expect an indication that choosing the option just duplicates the primary X-axis. What happens instead: There is no indication that the secondary X-axis does not work as expected. Perhaps I am wrong and the secondary X-axis can work as expected. I have found no evidence of that but would be happy to be corrected (and shown how it can work).
Update: It is possible to change the scale in a secondary X -axis. However, the version I was using (6.2.0.2) has some bugs in dealing with a secondary X axis. That is, it is only possible to change the scale to values from 0 to 100. I thought I had checked this in other versions but it looks like I did not. When reporting a bug, it is important to specify which versions are affected. I don't know why I did not do that or test this in other versions. I have now checked versions 6.1.6.3, 6.2.4.2, and 6.3. In all of those versions, it is possible to change the values to negative numbers and to numbers greater than 100. Thus, since it is possible to change the scale, the secondary X-axis is more useful than I thought. I will attempt to clarify what it does in the documentation. I now think that this bug report does not need to be acted upon. I don't know what the process is for indicating that a bug report can be disregarded and hope that someone else can do that. Apologies to the busy developers for having to spend time with this.
Hello Cathy, A new major release of LibreOffice is available since this bug was reported. Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Dear Cathy Crumbley, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear Cathy Crumbley, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp