Launchpad itself

Can't move a bug from product X to Y even if I'm a Y bug contact

Bug #72658 reported by Matthew Paul Thomas on 2006-11-21

This bug report is a duplicate of: Bug #34343: Shouldn't allow task or blueprint reassignment to an upstream that doesn't use Launchpad. Edit Remove

Affects		Status	Importance	Assigned to	Milestone
	Launchpad itself	New	Undecided	Unassigned

Bug Description

I cannot retarget a bug report from the wrong product to the right one, unless I'm a bug contact for the wrong product.

For example, I'm a member of (the team that is) the bug contact for Launchpad, but I don't have permission to move bug 70416 from launchpad-integration to launchpad.

Tags:

Revision history for this message

Diogo Matsubara (matsubara) wrote on 2006-11-29:

The problem here has nothing to do with being a bug contact. I teste in sample data and even you are a LP admin (Foo Bar) you, that field would be read-only.

The "product" field is read-only because launchpad-integration doesn't use malone as its official bugtracker.
I'm duping this against bug 34343

Report a bug

This report contains Public information

Everyone can see this information.

Duplicate of bug #34343 Remove

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

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