Error dialog needs to guide people to better bug reports

Bug #955294 reported by Martin Packman
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
QBzr
Confirmed
Medium
Unassigned

Bug Description

Too many bug reports form bzr gui users need extra prompting to get sufficient information on the error, bug 955197 is one example. We should be helping people file a good bug report first time around.

There was some work in bug 778012 to make the error handling in qbzr (which is also used by bzr-explorer) more useful, so we now do get errors as text rather than screenshots. In theory Ubuntu users should now be going through apport instead, but we get quite a lot of reports from windows users and others who use the information in the dialog only.

It would be nice to have a button that did a POST of the relevant data to launchpad, but a report link like <bzr-explorer/+filebug?field.title={sensible default name for bug}&field.actions.search> makes for a nicer landing than the current one used.

Also, even non-internal errors should have the full traceback and version info listed when expanding details, and probably the error message should appear in the initial view with some tidied up language to make it easier for people to simple problems (like connectivity) themselves.

Martin Packman (gz)
Changed in qbzr:
importance: Undecided → Medium
status: New → Confirmed
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.