---- Reported by lassi.ta.nieminen@nokia.com 2010-02-15 18:09:58 +0200 ---- Created an attachment testdata to be opened in kspread SOFTWARE VERSION: Kubuntu 9.10 Koffice (svn version 1088545) Test document (MS Excel 2003):mp03_intranet_group_cells.xls STEPS LEADING TO THE PROBLEM: 1. Open the attached document in MS Excel 2003. 2. Open the same document in KOffice. 3. Observe the grouping of cells in sheet1 * cells 6 to 19 and D to E are grouped. EXPECTED OUTCOME: Kspread should be able to display the grouped cells and data in it. see attachment ms03_intranet_cells_grouping_msexcel.PNG ACTUAL OUTCOME: Kspread is unable to display the grouped cells and data in it. The cells are missing. see attachment ms03_intranet_cells_grouping_kspread.png FREQUENCY: Always ---- Additional Comments From lassi.ta.nieminen@nokia.com 2010-02-15 18:11:47 +0200 ---- Created an attachment screenshot of the document in kpresenter ---- Additional Comments From lassi.ta.nieminen@nokia.com 2010-02-15 18:12:44 +0200 ---- Created an attachment screenshot of the document in msexcel ---- Additional Comments From lassi.ta.nieminen@nokia.com 2010-03-05 08:02:09 +0200 ---- Created an attachment pyodconverter converted testdata ---- Additional Comments From lassi.ta.nieminen@nokia.com 2010-03-05 08:02:27 +0200 ---- Created an attachment koconverter converted testdata ---- Additional Comments From lassi.ta.nieminen@nokia.com 2010-03-05 08:02:45 +0200 ---- Created an attachment koconverter converted testdata opened in openoffice ---- Additional Comments From lassi.ta.nieminen@nokia.com 2010-03-05 08:03:37 +0200 ---- Created an attachment pyodconverter converted testdata opened in koffice Observation (1096327) : File got corrupted when converted using koconverter and when loaded in open office error message is displayed. KOffice loaded the OOo-converted document properly, group cells functionality is not working --- Bug imported by faure@kde.org 2010-08-13 20:38 --- This bug was previously known as _bug_ 157042. Imported an attachment (id=50376) Imported an attachment (id=50377) Imported an attachment (id=50378) Imported an attachment (id=50379) Imported an attachment (id=50380) Imported an attachment (id=50381) Imported an attachment (id=50382)
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!