Search should rank exact matches as first rank
Bug #504676 reported by
Tomasz Chrzczonowicz
This bug affects 5 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
Low
|
William Grant |
Bug Description
How to reproduce:
1. Post a bug report or question.
2. Click edit next to "Affects" or "For:" respectively
3. Type "Launchpad" or some component, e.g. "Launchpad Bugs" in the text box
What happens:
You get huge amount of projects that seem to have nothing to do with Launchpad except being hosted there.
What this means:
If you want to assign/reasssign a bug/question to a Launchpad component, you need to know the codename for the component.
What should happen:
If you search for Launchpad, the first results should point to Launchpad and its components (rather than display results alphabetically, starting with Android and such)
Related branches
lp:~wgrant/launchpad/picker-sorting
- j.c.sackett (community): Approve
-
Diff: 352 lines (+176/-16)5 files modifiedlib/lp/bugs/javascript/bugtask_index.js (+2/-2)
lib/lp/registry/tests/test_person_vocabularies.py (+99/-4)
lib/lp/registry/tests/test_product_vocabularies.py (+26/-0)
lib/lp/registry/vocabularies.py (+45/-10)
lib/lp/services/features/flags.py (+4/-0)
affects: | malone → launchpad-answers |
description: | updated |
summary: |
- Searching for Launchpad (components) while editing "Affects" in Bug - Report and "For" in Answers is hopeless + Search overlay should top-post exact matches |
tags: | added: dhrb |
tags: | added: search |
summary: |
- Search overlay should top-post exact matches + Search should rank exact matches as first rank |
tags: | added: disclosure project-picker vocabulary |
Changed in launchpad: | |
assignee: | nobody → William Grant (wgrant) |
status: | Triaged → In Progress |
tags: |
added: qa-ok removed: qa-needstesting |
Changed in launchpad: | |
status: | Fix Committed → Fix Released |
tags: |
added: target-picker removed: project-picker |
To post a comment you must log in.
It might be worth fixing Bug #471328 when fixing this one.