Malone should include "documentation" on bug reporting

Bug #2574 reported by Øivind Hoel
6
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Medium
Brad Bollenbach

Bug Description

We se it all the time: Users scream about a crash here and a black screen there, with no proper debugging info. This is not because the people are too lazy to include this data, but because they don't know what to include and/or how to do it.

Take a look at opensuses submit a bug page: http://www.opensuse.org/Submit_a_bug - it details general info that's useful to include in different types of bug reports in a very accessible place: if you press the "report a bug" page on opensuse.org, you're brought to this page before you actually run into their bugzilla.

Perhaps Malone should be even more advanced in the sense that it provides more context-sensitive reporting information; ie if a user selects a gnome package, we provide the gnome and x-specific info to the user... In any case, a page like this (in a very obvious location) would seriously improve malone imho.

Tags: lp-bugs
Brad Bollenbach (bradb)
Changed in malone:
assignee: nobody → bradb
status: New → Accepted
Revision history for this message
Sitsofe Wheeler (sitsofe) wrote : Wiki links

Although from the side of people trying to resolve bug there's some pertinent information in https://wiki.ubuntu.com/Bugs/HowToApproachBugs which is part of https://wiki.ubuntu.com/HelpingWithBugs

Revision history for this message
Henrik Nilsen Omma (henrik) wrote :

FYI, I've started work on some very basic help pages on how to upload attachments. I'll extend this to other packages soon.

(yes, I think bug-reporting documentation should be package-specific)

https://wiki.ubuntu.com/DebuggingUbiquity/AttachingLogs

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.