To bug report pages add "fix this bug" link

Bug #588322 reported by Daniel Holbach on 2010-06-01
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Low
Unassigned

Bug Description

This would probably be a nice feature for all kinds of projects in Launchpad, as a start it would be nice if Ubuntu bugs would have a link somewhere that says "Fix this bug" or something similar that provides users with information how to fix this bug. https://wiki.ubuntu.com/Bugs/HowToFix for example would be a good start for those users.

Bryce Harrington (bryce) on 2010-06-04
Changed in malone:
importance: Undecided → Wishlist
status: New → Confirmed
status: Confirmed → Incomplete
Bryce Harrington (bryce) wrote :

I totally agree having a path exposed for users to get involved in fixing bugs is a great idea.

However I think this concept needs fleshed out a bit more before it can be considered to add to launchpad. For instance, where in the UI should the link go. Should it simply be a link to an external URL, or should there be an intermediate page in launchpad itself, that e.g. allows user to assign bug to themselves? Is "fix this bug" the best text for the link name, or will it trick users into thinking that the link will somehow result in someone else being more likely to fix it?

How would this work for non-Ubuntu projects using launchpad? Should there be some administrative UI for them to insert a different link? Inside launchpad, should this be something set at the product level, source-package level, or team level? If one of the latter two, how to handle bugs filed against multiple source packages?

An idea I've been kicking around is having launchpad include a method to trigger development environments to instantiate a project for the bug. For instance, it could trigger groundcontrol to fire up.

Daniel Holbach (dholbach) wrote :

A simple link would be a good first step. Of course this could be complicated to n-th degree: you could do a text-box where you could provide a recipe where $bugnr, $task_target, etc are substituted, how to remotely trigger groundcontrol I have no idea.

I set this bug to confirmed now, because we seem to agree that it's a good idea. However this is spec'ed out I leave to you dear LP Hackers.

Changed in malone:
status: Incomplete → Confirmed
Curtis Hovey (sinzui) on 2010-12-23
Changed in launchpad:
status: Confirmed → Triaged
tags: added: feature ui
Changed in launchpad:
importance: Wishlist → Low
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers