Bug tasks can be created with bare unsearchable Incomplete status
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
Low
|
William Grant | ||
Bug Description
I filed this bug today:
https:/
But it was not showing up in the bug list at <https:/
Only two bugs showed up there; though I noticed that the sidebar on this page lists 3 open bugs.
The bug was filed using the somewhat atypical url 'https:/
On a hunch, I went into the bug, changed its status to 'New', then back to 'Incomplete'.
It appears that internally, Launchpad allows a bug to be opened in state 'Incomplete' instead of in state 'Incomplete (without response)', but that this bug will then not show up in the index because this is not one of the bug states shown by default (and not even a state that's selectable from the advanced bug search).
I think +filebug should either disallow 'field.
Related branches
- Colin Watson (community): Approve
-
Diff: 197 lines (+91/-16)4 files modifiedlib/lp/bugs/model/bugtask.py (+16/-10)
lib/lp/bugs/model/tests/test_bugtask.py (+16/-1)
lib/lp/bugs/tests/test_bug_messages.py (+51/-1)
lib/lp/testing/factory.py (+8/-4)
| summary: |
- bugs missing from package bug index + Bug filing API can set bare unsearchable Incomplete status |
| Changed in launchpad: | |
| importance: | Undecided → Low |
| status: | New → Triaged |
| tags: | added: api bugs |
| summary: |
- Bug filing API can set bare unsearchable Incomplete status + Bug tasks can be created with bare unsearchable Incomplete status |
| Changed in launchpad: | |
| assignee: | nobody → William Grant (wgrant) |
| status: | Triaged → In Progress |
| Launchpad QA Bot (lpqabot) wrote | #1 |
| tags: | added: qa-needstesting |
| Changed in launchpad: | |
| status: | In Progress → Fix Committed |
| tags: |
added: qa-ok removed: qa-needstesting |
| Changed in launchpad: | |
| status: | Fix Committed → Fix Released |
Fixed in stable r18037 <http://