Summary: | easy / accurate bug filing | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | Jeff Aigner <jaigner> |
Component: | LibreOffice | Assignee: | Jeff Aigner <jaigner> |
Status: | RESOLVED DUPLICATE | ||
Severity: | enhancement | CC: | jaigner, lemoyne.castle, LibreOffice |
Priority: | medium | Keywords: | needsDevEval |
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Crash report or crash signature: | Regression By: |
Description
Jeff Aigner
2011-06-09 18:56:26 UTC
(Added from easyhack wiki list: http://wiki.documentfoundation.org/Development/Easy_Hacks_Complete_List) Could someone help me build a list of information that should be collected when filing a bug? Do we need anything more than the following list? Automatically collected info (hidden from user): * LibreOffice version / build number * Architecture platform * Operating system version * Java version User entered info: * Bug description * Email (if they really wish to be notified of bug progress) We might even consider just calling this feature a 'feedback' feature, and simply collect whether it's a bug, positive feedback, or a feature suggestion, plus a short description of whatever the user is reporting. The feedback dialog of Firefox 4.x seems like a decent guide in this area. *** This bug has been marked as a duplicate of bug 39435 *** RESOLVED, FIXED or CLOSED bugs cant be KEYWORD NEEDINFO. EasyHack tags unification: only allowed in Whiteboard to make queries more easy and reliable Migrating Whiteboard tags to Keywords: (ProposedEasyHack -> needsDevEval) [NinjaEdit] |