To make things easier for bug reporter as well as reader and analyst, it would be helpful to have a short note above or below "Optionally attach a document or a screenshot. " which advices to better put screenshots into a Draw file and add information to each screenshot.
I recently got the advice myself and think this is really a simple way to improve the reporting for all people involved.
Operating System: All
Thank you for your report!
IMHO a valid and reasonable enhancement request, therefore set Status to NEW.
1) The only possible drawback of this enhancement could be that the additional hint might make the BSA page too complicated, so that the user looses orientation. I hope that this is not the case. But *if* this happens, I mean, if the page become too complex by adding the hint, I would recommend to omit it.
If in doubt, please ask on our UX advise mailing list.
> ...] which advices to better put screenshots into a
> Draw file and add information to each screenshot.
2) This should be especially recommended
a) if the bug reporter wants to add more than one screenshot,
which belong together,
b) if he/she needs to emphasize and/or comment specific parts
of the screenshot(s).
3) Instead of a Draw file, the reporter could also add comments directly into the raster image, and/or combine screenshots or cut-outs of them into a single raster image (both can be done by some image manipulation application). [Personally I prefer this way, because the result is a simple raster image (PNG, JPEG ...) image again, which can be viewed directly in the web browser; but this may be a matter of taste.]
There is now a link to extended information about how to create attachments. I don't want to add more info directly in the site to not overflow the user with "advise"
Hi Rob, thanks for the improvement. Such a text helps already.
May I a suggest to add "(zip-file)" after "test kit". Without Rainer's earlier comment at least I would not understand that "test kit" is a zip-file with various files in it.
When I clicked the "advanced information" I reached the wiki page but needed to loggin in again. This stops people from reading the information, thus creating mistakes which means avoidable work. Could it be arranged that the loggin in LibO bug report site allows also to see the wiki?
Migrating Whiteboard tags to Keywords: ( ProposedEasyHack -> needsDevEval, TopicWeb TopicQA)