oops summaries should have a easy link to file a bug in Launchpad (or the projects bugtracker?)

[Diogo Matsubara]

This is a half baked idea, but I'm registering it here so I won't forget.

The oops summary should have a small link near an oops offering to report that as a bug.

For instance:

301 AttributeError: 'unicode' object has no attribute 'render'
GET: 301 Robots: 0 Local: 299

    * 66 https://translations.launchpad.net/ubuntu/hardy/+menudata (DistroSeries:+menudata)
          o OOPS-913A1055, OOPS-913A1084, OOPS-913A1156, OOPS-913A172, OOPS-913A1763, OOPS-913A2002, OOPS-913A2055, OOPS-913A2130, OOPS-913A2419, OOPS-913A2561 __File this OOPS as a bug__

or something like that.

[Joey Stanford (joey)]

It would be great if we could identify like oopes and show the bug number in the report. e.g. this oops has happened 5 times and here's the bug report. OR This oops causing bug has caused a total of 15 oopses.

[Christian Reis (kiko)]

Well.. we could add the OOPS as a bug alias and check the existence of the bug alias when rendering the OOPS. But ultimately to do this you want to be able to store OOPS information in Launchpad, I think.

[Diogo Matsubara (matsubara)]

Joey's suggestions will be implemented by https://blueprints.edge.launchpad.net/oops-tools/+spec/oops-tools-link-to-bug and bug 255872.

[Robert Collins (lifeless)]

We probably want the bug tracker to be configurable a-la bzr's bugtracker support.