It is possible to give all user related arguments in a query on user related bugs
Bug #517476 reported by
Markus Korn
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
Steps to reproduce this bug:
1.) go to https:/
2.) enter "thekorn" in "Assignee", "Reporter", "commenter", "subscriber", and "Project, ... subscriber" fields
3.) click on "search"
the resulting page is https:/
This page shows two bugs which are unrelated to wgrant, because all user related query fields are overwritten.
Revision history for this message
| Gavin Panella (allenap) wrote | #1 |
| affects: | launchpad-registry → malone |
| Changed in malone: | |
| importance: | Undecided → Low |
| status: | New → Triaged |
Revision history for this message
| Markus Korn (thekorn) wrote | #2 |
| tags: | added: search |
Revision history for this message
| Gavin Panella (allenap) wrote | #3 |
| Changed in malone: | |
| importance: | Low → Medium |
| Changed in launchpad: | |
| importance: | Medium → Low |
| description: | updated |
| tags: | added: bug-search |
To post a comment you must log in.
I think this a fairly uncommon scenario, but it does show some a design problem in the search approach.
A "correct" way to solve this might be be to make the result an intersection of all the user-related bugs and those discovered from the specific search request. In other words, only search within the set of user-related bugs.
Perhaps a less surprising solution would be to show an error if all the user-related query fields are specified as users other than the context.