Link source package to project when adding a bug task?

[Matt Zimmerman]

I thought it might help to establish more package<->project links if this could be done quickly and easily when forwarding a bug:

On Thu, Jan 17, 2008 at 08:31:39AM -0200, <email address hidden> wrote:
> On Wed, Jan 09, 2008 at 10:52:28AM +0000, Matt Zimmerman wrote:
> > * If the package isn't linked to an upstream project, can that be done as
> > part of the process? If the user has the necessary privileges (what are
> > they?), can we add a checkbox to create the association?
>
> There are no privileges necessary (but deletion is now possible, so we
> can fix it in the UI if bogus links are created).
>
> This is a good idea -- is there a bug filed on this?

[Matthew Paul Thomas (mpt)]

This is the converse of bug 44052, which is about auto-suggesting the appropriate project based on existing packaging links.

[Curtis Hovey (sinzui)]

The annoying notification we show when we ask the user to choose a project is to a form that is very similar the this form. We have all the data when the user completes this form. I have a spike that adds a checkbox to the choose a project page and created the link when the user completes the multistep form

    [ X] Link the package to the upstream project?
        Always suggest this project when adding an upstream bug for this package.

I think there are some corner-cases that need looking into. For example, the same multistep form is used in project registation, so I suspect the checkbox should be reused.

[Launchpad QA Bot (lpqabot)]

Fixed in stable r11231 <http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/11231>.

[Curtis Hovey (sinzui)]

Fixed released in launchpad-project 10.08.