Bug 61505

Summary: FILESAVE overwrites individual fix formatting with cell range CONDITIONAL FORMATTING
Product: LibreOffice Reporter: Luca Cerone <luca_cerone>
Component: CalcAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED INVALID    
Severity: normal CC: LibreOffice
Priority: medium    
Version: 3.6.0.2 rc   
Hardware: Other   
OS: Linux (All)   
Whiteboard: BSA
Crash report or crash signature: Regression By:

Description Luca Cerone 2013-02-26 11:29:39 UTC
Problem description: 

Steps to reproduce:
1. Create two styles EvenRow and OddRow with  background colors (eg gray and white).
2. Apply conditional formatting to cells:
formula ISEVEN(ROW()) apply EvenRow
formula ISODD(ROW()) apply OddRow 
3. Clear the formatting of one of the cells and apply a different background color (eg yellow).
4. Save
5. Reload

Current behavior:
The cell that supposedly should have had yellow background
is loaded with the conditional background color rather
than with the right background color.

Expected behavior:
The background color should stay the same when reloading the file.
              
Operating System: Ubuntu
Version: 3.6.0.2 rc
Comment 1 Rainer Bielefeld Retired 2013-02-26 13:09:59 UTC
NOT reproducible with parallel Dev-installation of  "Version 4.1.0.0.alpha0+ (Build ID: fd56eb98e63b4aac12c9633d5847a3fb964f326) TinderBox: Win-x86@6, Branch:master, Pull Time: 2013-02-22_21:43:36" ENGLISH UI / German Locale  on German WIN7 Home Premium (64bit) with LODev/4 Masters User Profile 

but reporter's description is much to imprecise for any conclusion.

@Luca Cerone 
Thank you for your report – unfortunately important information is missing.
May be hints on <http://wiki.documentfoundation.org/BugReport> will help you to find out what information will be useful to reproduce your problem? 
Please add all information requested in following:
- Write a meaningful Summary describing exactly what the problem is
  "Saving spreadsheet with background colors " is not the description of a 
  problem"
- Attach a sample document (not only screenshot) or refer to an existing 
  sample document in an other Bug with a link; to attach a file to this 
  bug report, just click on "Add an attachment" right on this page.
- Attach screenshots with comments if you believe that that might explain the 
  problem better than a text comment. Best way is to insert your screenshots
  into a DRAW document and to add comments that explain what you want to show
  (attachment 68877 [details], attachment 68490 [details])
- Contribute a document related step by step instruction containing every 
  key press and every mouse click how to reproduce your problem 
  (similar to example in Bug 43431)
– if possible contribute an instruction how to create a sample document 
  from the scratch
- add information 
  -- what EXACTLY is unexpected
     What cell? first or second condition? ...
  -- concerning your Operating System (Version, Distribution, Language)
  -- concerning your LibO version (with Build ID if it's not a public release)
     and localization (UI language, Locale setting)
  –- Libo settings that might be related to your problems 
    (video hardware acceleration, Experimental features enabled, ...)
  -- how you launch LibO and how you opened the sample document
  -- how you checked that it's not a FILEOPEN problem
  –- Whether your problem persists when you renamed your user profile 
     before you launch LibO (please see
     <https://wiki.documentfoundation.org/UserProfile#User_profile_location>)
  –- If you can contribute an AOOo Issue that might be useful
  -- everything else crossing your mind after you read linked texts
Comment 2 Rainer Bielefeld Retired 2013-02-26 13:10:55 UTC
(In reply to comment #1)
oops, please ignore the "AOOo Issue" item!
Comment 3 QA Administrators 2013-09-24 01:59:01 UTC
Dear Bug Submitter,

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 2013-10-25 15:19:53 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
Comment 5 QA Administrators 2013-10-25 16:18:48 UTC
Apologies - these were accidentally set to FIXED instead of INVALID - sorry for the noise