Launchpad itself

Shouldn't allow task or blueprint reassignment to an upstream that doesn't use Launchpad

Bug #34343 reported by Brad Bollenbach
32
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

I reassigned a bug to bzrtools, by editing the product field on +editstatus. It turns out that bzrtools doesn't use Malone, so I should have gotten an error message when I reassigned it.

Steps to reproduce (using sample data):
1. Open http://launchpad.dev/products/firefox/+bug/1/+editstatus;
2. Change the product to "thunderbird" (a product that doesn't use malone officially);
3. Click "Save Changes";
4. End up with a read-only upstream bugtask.

See original description
Brad Bollenbach (bradb)
Changed in malone:
assignee: nobody → bjornt
status: Unconfirmed → Confirmed
Revision history for this message
Matt Zimmerman (mdz) wrote :

This should be allowed; we do this in Ubuntu to record the fact that a bug is an upstream bug, regardless of whether the upstream uses Malone. Per discussions with Mark, this is also a good idea because it provides useful content for upstreams who come looking for it.

It should perhaps be made clear to the user what they can expect from this action, but it shouldn't be disallowed

Revision history for this message
Matthew Paul Thomas (mpt) wrote :

We don't allow the creation of such bug reports directly because that would mislead people into reporting bugs that were never noticed. Why wouldn't the same apply to creating them indirectly by changing the product field?

Revision history for this message
Brad Bollenbach (bradb) wrote :

mdz, I mean that a brand new bug filed on product foo should not be able to be reassigned to product bar, by editing the product in the expandable form, if bar doesn't use Malone officially.

I believe you're thinking of adding an upstream to an Ubuntu bug with the "Also affects:" links, which is a different use case.

Diogo Matsubara (matsubara)
description: updated
Björn Tillenius (bjornt)
Changed in malone:
assignee: Björn Tillenius (bjornt) → nobody
Revision history for this message
Matthew Paul Thomas (mpt) wrote :

This bug just wasted me five minutes: I was looking for a bug report on the Ubuntu Software Store, and eventually discovered that it had been moved from the gnome-app-install project to the software-store project despite the software-store project not using Launchpad for bugtracking.

Curtis Hovey (sinzui)
Changed in blueprint:
status: New → Triaged
importance: Undecided → Low
summary: - Shouldn't allow task reassignment to an upstream that doesn't use Malone
+ Shouldn't allow task or blueprint reassignment to an upstream that
+ doesn't use Malone
summary: Shouldn't allow task or blueprint reassignment to an upstream that
- doesn't use Malone
+ doesn't use Launchpad
Robert Collins (lifeless)
Changed in launchpad:
importance: Medium → High
Curtis Hovey (sinzui)
Changed in launchpad:
importance: High → Low
tags: added: target-picker
Revision history for this message
Matthew Paul Thomas (mpt) wrote :

This is a duplicate of bug 333215, which despite being much newer, has more information about how to fix the bug, and even a cursory patch.

However, Curtis resummarized this bug to cover blueprints as well, which bug 333215 does not. It seems unlikely that Blueprint would be fixed by the same code change, so perhaps this bug report should morph to cover blueprints only.

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

Duplicates of this bug

Subscribing...

Other bug subscribers

Related blueprints

Remote bug watches

Bug watches keep track of this bug in other bug trackers.