I have to search twice before i can create a new project that's "also affected" by a bug
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
I record a bug as affecting another project. I enter the name of a nonexistent project. Error message is "There is no project in Launchpad named "xxx". Please search for it as it may be registered with a different name."
From my point of view, I just searched for it--that's how Launchpad knows there's no such project. Clicking on 'search for it' brings up a form that, for all I know, just does the same search again. And I can't create the project without first clicking 'search for it', which I'm disinclined to do.
Something more like the bug duplicate workflow would be more friendly. Automatically do the second search (a keyword search) if the name match fails, and say either:
There is no project in Launchpad named "xxx". Did you mean one of these projects?
* p1
* p2
If none of these projects are the one you're thinking of, _search for it under a different name_, or _create a new project_.
or:
No project in Launchpad was found matching 'xxx'. _Search for the project under a different name_, or _create a new project_.
| Changed in launchpad: | |
| status: | New → Confirmed |
| James Henstridge (jamesh) wrote | #1 |
| Changed in malone: | |
| importance: | Undecided → Low |
| status: | Confirmed → Triaged |
The "search for it" link does the same as the "(Choose...)" link that was available on the initial form.
We've talked in the past about replacing the "(Choose...)" search thingee with an AJAX drop down list similar to Google Suggest, but haven't gotten round to it. Your workflow sounds like an interesting workflow for the non-AJAX case though.