canmove, Confirmed users
432
edits
Bugzilla Fixup: Difference between revisions
Jump to navigation
Jump to search
→Suggestions/nominations
| Line 35: | Line 35: | ||
= Suggestions/nominations = | = Suggestions/nominations = | ||
* roc: user profile checkboxes to control whether or not each user is currently accepting review requests of each type; ONLY those users are accepted as review request targets. No more blank/blackholed review requests. Use only those users for autocompletion of partial names, of course. (+ | * roc: user profile checkboxes to control whether or not each user is currently accepting review requests of each type; ONLY those users are accepted as review request targets. No more blank/blackholed review requests. Use only those users for autocompletion of partial names, of course. (+2) | ||
* callek: Per Product/Component "watches" rather than a user needing to know a default QA/Assignee for the product/component. | * callek: Per Product/Component "watches" rather than a user needing to know a default QA/Assignee for the product/component. (+1) | ||
** callek: Ability for bug "moves" to generate mail when entering+leaving said product/component. | ** callek: Ability for bug "moves" to generate mail when entering+leaving said product/component. | ||
* dbaron: user nicknames (user-chosen, system-unique) that, when entered exactly, take priority over autocomplete in cc: and review requests (+1) | * dbaron: user nicknames (user-chosen, system-unique) that, when entered exactly, take priority over autocomplete in cc: and review requests (+1) | ||
* reed: I have a list of bugs I've wanted in bmo for a while tagged with the "[wanted-bmo]" tag in the status whiteboard. Check out the list [http://tinyurl.com/2z8swt here]. | * reed: I have a list of bugs I've wanted in bmo for a while tagged with the "[wanted-bmo]" tag in the status whiteboard. Check out the list [http://tinyurl.com/2z8swt here]. | ||
* faaborg: export search results to JSON and provide a front end to the search results based on [http://simile.mit.edu/exhibit/ MIT's Exhibit] so users can do faceted browsing on the data. Here is an example of the [https://people.mozilla.com/~mconnor/PRD.html Firefox 3 PRD in exhibit] (+1) | * faaborg: export search results to JSON and provide a front end to the search results based on [http://simile.mit.edu/exhibit/ MIT's Exhibit] so users can do faceted browsing on the data. Here is an example of the [https://people.mozilla.com/~mconnor/PRD.html Firefox 3 PRD in exhibit] (+1) | ||
* gavin: {{bug|251556}} - proper regression tracking, distinct from "blocked/depends on" tracking. I've been wanting this forever, and I think the cost/benefit ratio for fixing it is very low. (+ | * gavin: {{bug|251556}} - proper regression tracking, distinct from "blocked/depends on" tracking. I've been wanting this forever, and I think the cost/benefit ratio for fixing it is very low. (+2) | ||
* shaver: REST (contra: XML-RPC) APIs for search and bug manipulation (but especially search!) (+1) | * shaver: REST (contra: XML-RPC) APIs for search and bug manipulation (but especially search!) (+1) | ||
* cbarrett: Ability to receive different bugmail for watches. i.e. I want to get email when a new bug is filed in widget:cocoa, and I want to see when smichaud, josh, or shebs attach patches, but not any of their other activity. | * cbarrett: Ability to receive different bugmail for watches. i.e. I want to get email when a new bug is filed in widget:cocoa, and I want to see when smichaud, josh, or shebs attach patches, but not any of their other activity. | ||
| Line 47: | Line 47: | ||
** These are not "restrictions", they are intentional. There are long discussions in bugs about why they are both a good idea. (Just so you know.) | ** These are not "restrictions", they are intentional. There are long discussions in bugs about why they are both a good idea. (Just so you know.) | ||
* gerv: what does "New UI for bugzilla using the API" mean? A XUL client? Ajax? | * gerv: what does "New UI for bugzilla using the API" mean? A XUL client? Ajax? | ||
* dolske: Integrate with [[Build:TryServer]], to allow submitting a patch directly from Bugzilla | |||
* dolske: Integration with CVS/Hg and LDAP, so that users with checkin powers can do directly from Bugzilla (w/ checkin messages autogenerated). Future work could add warnings (or errors) if you're trying to checkin something without appropriate review and approval. And, vice versa, if something is checked into a repository without a corresponding bug. | |||