| Summary: | No way to search for completed bugs via the Simple Search page | ||
|---|---|---|---|
| Product: | [Infrastructure] Bugzilla | Reporter: | Darren Hart <dvhart> |
| Component: | bugzilla | Assignee: | Yongkang You <yongkang.you> |
| Status: | VERIFIED NOTABUG | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | infras.bug.watcher, Infras.watcher, sgw |
| Version: | unspecified | ||
| Target Milestone: | Q4 | ||
| Hardware: | All | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | --- | |
|
Description
Darren Hart
2011-08-17 08:06:39 UTC
Add Saul in cc list. Who can help on this bug? Not sure this can be adjusted through admin page. I guess it needs to modify bugzilla codes. Just FYI. Since bugzilla 4.0, "Close" is not the default bug stage after install a new bugzilla: """ https://bugzilla.mozilla.org/show_bug.cgi?id=486292 The default workflow has been changed. New installations will now have UNCONFIRMED, CONFIRMED, IN_PROGRESS, RESOLVED and VERIFIED as bug statuses instead of the old UNCONFIRMED, NEW, ASSIGNED, REOPENED, RESOLVED, VERIFIED and CLOSED bug statuses. You are of course free to edit them from the administrative pages if you don’t like the new default workflow. """ BTW, better to change the default assignee for Bugzilla product. :) As it turns out, selecting Status=Closed returns a list of bugs with Status=(Resolved|Verified|Closed). This is rather non-intuitive, but it makes sense to search for completed bugs and get those three states. We can close this as NOT_A_BUG unless others find this confusing as well. (In reply to comment #2) > As it turns out, selecting Status=Closed returns a list of bugs with > Status=(Resolved|Verified|Closed). This is rather non-intuitive, but it makes > sense to search for completed bugs and get those three states. We can close > this as NOT_A_BUG unless others find this confusing as well. Totally agree. :) Given the functionality exists and taking Yongkang's comments into account, I think we can "close" this without any further action. Based on Darren's comment. Mark this bug to be "closed" stage. |