Blueprint dependency picker doesn't allow searching outside the target
Bug #707111 reported by
James Westby
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
Critical
|
Tim Penhey |
Bug Description
It's now possible to have a dependency on a blueprint in another project.
However, it's not possible to find that blueprint using the picker on the
"Add dependency" page.
This makes it undiscoverable, and hard to know how to use the feature even if
you know it exists.
Obviously care needs to be taken to show useful results.
Thanks,
James
Related branches
lp:~thumper/launchpad/blueprint-dependencies
- Robert Collins (community): Approve
- Diff: 0 lines
lp:~thumper/launchpad/blueprint-dependency-vocabulary
- Michael Hudson-Doyle: Approve
-
Diff: 370 lines (+134/-156)4 files modifiedlib/lp/blueprints/vocabularies/specificationdependency.py (+65/-42)
lib/lp/blueprints/vocabularies/tests/specificationdepcandidates.txt (+0/-97)
lib/lp/blueprints/vocabularies/tests/test_doc.py (+0/-17)
lib/lp/blueprints/vocabularies/tests/test_specificationdependency.py (+69/-0)
Changed in launchpad: | |
status: | Triaged → In Progress |
assignee: | nobody → Tim Penhey (thumper) |
Changed in launchpad: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
I thought we explicitly excluded blueprints from different pillars? Anyhow, marking low for now as blueprints is used by a very small fraction of our users.