Register a product while adding an upstream task

Bug #127126 reported by Björn Tillenius
6
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Guilherme Salgado

Bug Description

When add an upstream task to a bug, and the upstream product is not yet registered in Launchpad, you get an error message telling you to register it. It's quite a lot of work doing that, so instead we should offer the possiblity to register the project while adding the upstream task at the same time.

We should prompt the user for as little information as possible.

Changed in malone:
assignee: nobody → salgado
Changed in malone:
importance: Undecided → High
status: New → Confirmed
description: updated
Changed in malone:
status: Confirmed → In Progress
Changed in malone:
milestone: 1.1.10 → 1.1.11
Revision history for this message
Guilherme Salgado (salgado) wrote :

We initially decided to ask only for the name, display name and summary, but since the last release (1.1.10) there's a new requirement to create a new project --the licenses in which the project's code is released, so we'll have to ask for that as well.

Revision history for this message
William Grant (wgrant) wrote : Re: [Bug 127126] Re: Register a product while adding an upstream task

On Fri, 2007-10-26 at 19:21 +0000, Guilherme Salgado wrote:
> We initially decided to ask only for the name, display name and summary,
> but since the last release (1.1.10) there's a new requirement to create
> a new project --the licenses in which the project's code is released, so
> we'll have to ask for that as well.

That seems to remove the whole quickness of the registration - I don't
particularly want to have to trawl through the code for every license.

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

Salgado: just because we require licenses on /projects/+new, it doesn't mean we need to require it when creating the project while adding a bugtask. The idea about this bug is that it should be really simply register a new project, so we should try keeping it simple. Finding out which license a project uses it not always that simple.

We do have projects with no license specified, so it shouldn't be a problem, they can specify it later.

Revision history for this message
Guilherme Salgado (salgado) wrote :

On Tue, Oct 30, 2007 at 03:04:37PM -0000, Björn Tillenius wrote:
> Salgado: just because we require licenses on /projects/+new, it doesn't
> mean we need to require it when creating the project while adding a
> bugtask. The idea about this bug is that it should be really simply
> register a new project, so we should try keeping it simple. Finding out
> which license a project uses it not always that simple.
>

The only problem is that the existing API for creating teams has been
changed to not allow new teams to be created without at least one license,
although I'm sure kiko will be okay with us relaxing that restriction.

> We do have projects with no license specified, so it shouldn't be a
> problem, they can specify it later.

That's right, and maybe we'd want to send a mail notification to feedback@
when a new project is created through this workflow, like we do when
the user chooses one of the OTHER* licenses at the time the project is
created on /projects/+new?

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

Is there any reason for us to want to know the license for new projects but not for existing projects? If not, having existing projects with no license specified is something we should phase out (as we have previously discussed), so it's not a precedent for allowing license-less project registration when bug-tracking.

Revision history for this message
Guilherme Salgado (salgado) wrote :

My understanding was that the plan was to phase out projects without
licenses, but both Kiko and Bjorn think it's okay to not require the license
for projects registered through the also-affects-upstream workflow.

Changed in malone:
milestone: 1.1.11 → 1.1.12
Revision history for this message
Guilherme Salgado (salgado) wrote :

landed on mainline r5243

Changed in malone:
status: In Progress → Fix Committed
Revision history for this message
Francis J. Lacoste (flacoste) wrote :

Released in 1.1.12.

Changed in malone:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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