Make it easy to mark bugs as being sent upstream

Bug #5409 reported by James Henstridge
This bug report is a duplicate of:  Bug #1208: Linking to remote bug is very awkward. Edit Remove
4
Affects Status Importance Assigned to Milestone
Launchpad itself
New
Medium
Unassigned

Bug Description

In the bugzilla importer, we represent bugs as having been sent upstream as follows:
 * create a new bug task on the upstream product associated with the distro package.
 * create a bug watch based on the upstream bugtracker URL
 * link the bug watch to the bug task.

Performing all these actions manually through the web UI is time consuming, and could be a lot simpler.

It would be nice if there was a "filed upstream" link on the bug page for distro bugs that would ask for a bug tracker URL, and create the new bug task and watch for you.

Revision history for this message
Björn Tillenius (bjornt) wrote : Re: [Bug 5409] Make it easy to mark bugs as being sent upstream

In https://wiki.launchpad.canonical.com/BetterUpstreamHandling, there
are some thoughts about how to make it easier to indicate that bugs are
sent upstream.

Revision history for this message
James Henstridge (jamesh) wrote :

Interesting. For reference, the bugzilla importer creates the bug watch using IBugWatchSet.fromText() on a bugtracker URL (which will create the bug tracker entry if necessary).

Handling a simple bug number might be a little more difficult, since currently there is a one to many relationship between projects and bug trackers. So going package -> product -> project -> bug tracker can give multiple results.

Revision history for this message
Björn Tillenius (bjornt) wrote :

On Wed, Dec 07, 2005 at 07:22:53AM -0000, James Henstridge wrote:
> Public bug report changed:
> https://launchpad.net/malone/bugs/5409
>
> Comment:
> Interesting. For reference, the bugzilla importer creates the bug watch
> using IBugWatchSet.fromText() on a bugtracker URL (which will create the
> bug tracker entry if necessary).
>
> Handling a simple bug number might be a little more difficult, since
> currently there is a one to many relationship between projects and bug
> trackers. So going package -> product -> project -> bug tracker can
> give multiple results.

Yeah, it's not that well thought through yet, it's mostly some rough
thoughts, there wasn't time at UBZ to refine them. Currently not all
products are even part of a project, and thus cannot be associated with
any bug tracker, which seems kind of broken. I would rather see that
one could go package -> product -> bug tracker directly, using the
project bug tracker(s) as a fall back.

Or, maybe specifying an URL is enough. That's probably easier and less
error prone in a lot of cases, since you tend to copy and paste URLs,
but you don't do that with bug numbers, at least I don't.

Revision history for this message
Christian Reis (kiko) wrote :

Yeah, I think a URL is probably the way to go. It would involve parsing the URL, trying to locate a registered bugtracker with the provided hostname, and then using something like the dictionary in BugWatch.url() to grab the actual bug id.

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

Other bug subscribers

Related blueprints