https://bugs.documentfoundation.org/show_bug.cgi?id=92444
--- Comment #3 from steve -_- <[email protected]> --- @mal: rule of thumb: one problem per bug. Otherwise things escalate quickly and it get's really hard to keep track of anything at all. If you have a document which has 6 problems, open 6 reports. Interlinking the reports via the "see also:" field might be a good idea then. But generally speaking: if you run into trouble it's always good to report the problem. That's the first step to improve the situation. QA will then deal with your reports i.e. mark them duplicates or valid + new etc. As for filing good bug reports, this Wiki is a good starting point: https://wiki.documentfoundation.org/QA/BugReport "looking bad" is not a good description. The more specific you can be the better. And giving good reproduce steps and clearly indicating what QA / devs should be looking for in the title of your bug + the description will help a lot to move things forward faster. -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
