Error pages should have better advice about reporting bugs

Bug #3578 reported by Jeff Bailey on 2005-10-25
18
Affects Status Importance Assigned to Milestone
Launchpad itself
Medium
Matthew Paul Thomas

Bug Description

Launchpad's error pages now include OOPS codes for reporting bugs. As a result, the pages need a bit of tweaking.
* The suggestion to include the URL in a bug report should be replaced by the suggestion to include the OOPS code.
* The 404 page should downplay the possibility of reporting bugs. Our internal 404 reports provide better information, and allow for better prioritization of bugfixes, than externally-contributed bug reports do.

Dafydd Harries (daf) wrote :

I think the OOPS system James implemented helps a lot here: it allows us to get a traceback which makes tackling the problem a lot quicker. However, some OOPSes are just 404s, so I think filing a bug each time probably isn't the right thing to do.

Subscribing Steve and James since they've been thinking about error reporting a lot recently.

Jeff Bailey (jbailey) wrote :

Right. My issue here is more the end user experience. I haven't seen a bug page in a while (And congrats for this!), but it used to say "report a bug", and then not give any hints as to what I might report.

It always felt like being the IT guy staring at the Windows errors that said "Talk to your administrator" =)

What I imagine is something like "Hey! You've found a bug. Please report a bug saying that at @DTIME@, you got a system error with @SESSION_HANDLE@, at @URI@. We'll be able to track everything else down with that. Thanks for using Launchpad!"

At that point I feel confident that I'm actually being helpful and usefully part of the process.

Tks,
Jeff Bailey

Steve Alexander (stevea) wrote :

Jeff,

Try going to https://launchpad.net/some_page_we_dont_have

This is the not found page, a specific example of an error page you might encounter, maybe from a bad link within launchpad.

Does this work for you now?

Changed in launchpad:
status: New → NeedInfo
Steve Alexander (stevea) wrote :

On the "oops" 404 page, it is not obvious to me that I can report a bug concerning launchpad by clicking the "help us improve" link at the bottom of the page. I think the "oops" pages should explicitly say "there are links to report bugs on the _help us improve_ link" or something like that.

Changed in launchpad:
assignee: nobody → mpt

On 12/16/05, Jeff Bailey <email address hidden> wrote:
> Public bug report changed:
> https://launchpad.net/malone/bugs/3578
>
> Comment:
> Right. My issue here is more the end user experience. I haven't seen a
> bug page in a while (And congrats for this!), but it used to say "report
> a bug", and then not give any hints as to what I might report.
>
> It always felt like being the IT guy staring at the Windows errors that
> said "Talk to your administrator" =)
>
> What I imagine is something like "Hey! You've found a bug. Please
> report a bug saying that at @DTIME@, you got a system error with
> @SESSION_HANDLE@, at @URI@. We'll be able to track everything else down
> with that. Thanks for using Launchpad!"
>
> At that point I feel confident that I'm actually being helpful and
> usefully part of the process.

This is an interesting idea. It reminds me of the sample email the
WordPress developers offer up in the "Requirements" section:

  http://wordpress.org/about/requirements/

(Wordpress provides excellent "feel-good documentation", IMHO. :)

Maybe it would be interesting to extend Jeff's idea into providing
copy-and-pasteable sample wording for the bug report with OOPS code
and provide a link directly to the Launchpad product +filebug page?
(In the hopefully not too distant future, +filebug would be a guided
filebug workflow to help reduce duplicate bug reports.)

Cheers,

--
Brad Bollenbach

description: updated
Matthew Paul Thomas (mpt) wrote :

Now we're getting daily summaries of the most common page display failures, it's not necessary for people using Launchpad to report bugs on them any more. I'm changing this to suggest making a support request if a particular error is holding up your work.

Changed in launchpad:
status: Needs Info → In Progress
Changed in launchpad:
status: In Progress → Fix Committed
Dafydd Harries (daf) on 2006-02-21
Changed in launchpad:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Related blueprints