<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTABUG - opposite result in conditional formatting in LibO Calc" href="https://bugs.documentfoundation.org/show_bug.cgi?id=91070#c38">Comment # 38</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTABUG - opposite result in conditional formatting in LibO Calc" href="https://bugs.documentfoundation.org/show_bug.cgi?id=91070">bug 91070</a> from <a class="email" href="mailto:markus.mohrhard@googlemail.com" title="Markus Mohrhard <markus.mohrhard@googlemail.com>"> Markus Mohrhard</a> <pre>(In reply to Buovjaga from <a href="show_bug.cgi?id=91070#c37">comment #37</a>) > Sorry, I will close this per discussion with Markus. > > This report has become too much a wandering investigation. If you can > describe the problem crystal clearly now, please open a new report. You can > CC me to it. To add to this. Add a detailed instruction to the bug report with steps that are idiot proof. What do you expect and why? Keep in mind that as a developer we look differently at this report than a user or QA (e.g. I checked the XLS file with a binary XLS inspection tool). Having detailed steps helps us quickly judge if a report is worth further inspection with additional tools or if other bugs (regressions) are more important right now. Normally the time that is required to understand a bug report is directly proportional to the change of the bug being fixed.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>