Bug 58030

Summary:	EDITING: Charts break when renaming sheet while charts are hidden in collapsed rows with autofilter
Product:	LibreOffice	Reporter:	thinkerix
Component:	Calc	Assignee:	Not Assigned <libreoffice-bugs>
Status:	RESOLVED INVALID
Severity:	normal
Priority:	medium
Version:	3.6.3.2 release
Hardware:	x86-64 (AMD64)
OS:	Windows (All)
Whiteboard:
Crash report or crash signature:		Regression By:

Description thinkerix 2012-12-08 19:08:38 UTC

I am not able to reproduce this error with a new small and fresh test-file, but the error that I faced with my working file was the following:

Problem description:

1. I am having a file with 5 sheets

2. One of those sheets has >1000 lines and >20 columns

3. In the first column I have entered "menu" data, which means that I enter different keywords to each line and then place an auto-filter to this column. This way I can hide and show lines via the autofilter-menu. This is like a menu emulation for different levels of detail

4. In the deepest level of detail I am having 80 charts which relate to data inside the same sheet

5. After having selected a level of detail in which those charts are not visible (i.e. hidden by the autofilter) and RENAME the sheet, at some later moment, after having continued editing, saving, closing and re-opening the file multiple times, I realized that most of the charts are broken!

6. The charts are empty and do not relate to any data. I can not select the "Data Ranges.." menu item from the context menu either, since this option is not existing anymore. Instead of this, I have a new option now called "Chart Data Table" where I could manually enter chart data if I wanted.

7. I solved the problem by:
- Expanding all lines of the sheet, including the broken charts
- Rename the sheet to the previous name
- Save the file

8. After reopening the file, all charts where fixed again! I even could rename the sheet again to something else (while having all lines expanded!) and it would work fine

Regards

Comment 1 john.pratt 2012-12-21 16:06:15 UTC

Are you able to attach the problem file?

Comment 2 ign_christian 2013-06-10 06:22:22 UTC

Please change status to UNCONFIRMED after you attach that file

Comment 3 QA Administrators 2014-02-02 02:06:30 UTC

Dear Bug Submitter,

Please read the entire message before proceeding.

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 INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here: 
https://wiki.documentfoundation.org/QA/FDO/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

Comment 4 QA Administrators 2014-02-26 19:31:01 UTC

Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID 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 FDO