Bug 54400 - Conditional FORMATTING references
Summary: Conditional FORMATTING references
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
3.6.0.4 release
Hardware: Other Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on: 55710
Blocks:
  Show dependency treegraph
 
Reported: 2012-09-02 18:49 UTC by Otto Zorro
Modified: 2013-10-25 15:13 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
an example spedsheet to show the problem "conditional Formatting" under LO3.6 (9.34 KB, application/vnd.oasis.opendocument.spreadsheet)
2012-09-02 18:49 UTC, Otto Zorro
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Otto Zorro 2012-09-02 18:49:22 UTC
Created attachment 66501 [details]
an example spedsheet  to show the problem "conditional Formatting" under LO3.6

Problem description: 

Steps to reproduce:
1. create a conditional Formatting like (example in A2) if cellvalue = A1
2. copy it down, it doesn't work, the Adress is not relativ
3. in LO 3.5 it works well

Current behavior: the Celladress is not relativ

Expected behavior: copy like LO3.5

Platform (if different from the browser): 
              
Browser: Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:15.0) Gecko/20100101 Firefox/15.0
Comment 1 Jean-Baptiste Faure 2012-09-16 06:21:51 UTC
Your file (https://bugs.freedesktop.org/attachment.cgi?id=66501) crashes LO 3.6.2.1 and LO 3.6.3.0+ :-(

Please explain how you did your conditional formatting.

Best regards. JBF
Comment 2 Rainer Bielefeld Retired 2012-10-07 05:48:38 UTC
"Copy it down"? I can open the sample document with 3.6.0.4 (WIN), but no idea how to reproduce the problem. 

@Otto Zorro 
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? If you believe that that  is really sophisticated please as for Help on a user mailing list
Please:
- Write a meaningful Summary describing EXACTLY what the problem is
- 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
- 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
  -- and WHY do you believe it's unexpected (cite Help or Documentation!)
  -- concerning your OS (Language)
  -- concerning your LibO (UI language, Locale setting)
  –- Libo settings that might be related to your problems 
  -- how you launch LibO and how you opened the sample document
   -- everything else crossing your mind after you read linked texts
Comment 3 Michael Meeks 2012-10-08 19:11:52 UTC
To get anywhere here we'd need bug#55710 resolved I suspect.
Comment 4 Markus Mohrhard 2012-10-08 22:06:39 UTC
(In reply to comment #3)
> To get anywhere here we'd need bug#55710 resolved I suspect.

No, The problem in Bug 55710 is only import of old style conditional formats. This bug does not affect conditional formats.

I'll try to go through all the conditional format bugs that show up in my list as soon as I finished the refactoring of the conditional format dialogs and cell attribute storing of conditional formats.
Comment 5 Julien Nabet 2013-01-22 20:41:30 UTC
On pc Debian x86-64 with 3.6 sources updated some days ago, I could:
- open the file
- selected the line and copied down so in column F, I had E3*B3, E4*B4, etc.

Perhaps I missed something.

Any update about this one?
Comment 6 QA Administrators 2013-09-24 01:54:47 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 7 QA Administrators 2013-10-25 15:13:29 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