https://bugs.documentfoundation.org/show_bug.cgi?id=91070
--- Comment #38 from Markus Mohrhard <[email protected]> ---
(In reply to Buovjaga from comment #37)
> 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.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
