Account confirmers, Anti-spam team, Confirmed users, Bureaucrats and Sysops emeriti
4,925
edits
BugzillaImprovements: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 94: | Line 94: | ||
Would it be crazy to propose being able to vary the presence and default state of all the fields on a per-product basis? -- zw. | Would it be crazy to propose being able to vary the presence and default state of all the fields on a per-product basis? -- zw. | ||
===Integrate Comments Into Bug History=== | |||
If I'm reading a bug report for the first time, and trying to familiarize myself with what has happened on the bug so far, it's hard to know what actions in the bug comments correspond with what action in the bug history (renaming, changing component, change of status, etc.). If you could incorporate bug history and bug comments[1], it would make it much easier to put the bug history and comments into context. -- Chris Ilias. | |||
* [https://bugzilla.mozilla.org/show_bug.cgi?id=11368 Bug 11368] - Move all bug activity onto main bug screen. | |||
===Keyword Subscriptions=== | |||
The ability to subscribe to keywords. -- Chris Ilias | |||
* [https://bugzilla.mozilla.org/show_bug.cgi?id=278455 Bug 278455] - Ability to "watch" based on any field. | |||
==="Next Action"=== | |||
I want "next action" and "next action assignee" fields (replacing | |||
several existing fields). Then each contributor will be able to find | |||
bugs they can help with, and fewer bugs will fall into the trap of | |||
being part of an unmanageable "pile of stuff". | |||
Bernd, Chris Lawson, alanjstr, Frederic Wenzel, and Brendan Eich are | |||
all enthusiastically in support of this proposal. | |||
http://www.squarefree.com/2009/04/20/getting-bugs-done/ | |||
http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/aa627caed996d9bc | |||
| Line 160: | Line 186: | ||
== Speed == | == Speed == | ||
Lots of people requested that Bugzilla be made faster, and suggested a number of ways that this could be achieved. However, we should test before optimizing. Some possibilities, though: | |||
* Template Toolkit buffers all output, although in the past b.m.o. has had flushing hacks -- bbaetz. | |||
* MySQL doesn't support cursors, so any select result has to entirely be pulled out of the DB, so it wouldn't be possible to display the output of buglists as it comes anyway. -- bbaetz. | |||
* Reduce page weight for show_bug. | |||
=== Parallelization === | === Parallelization === | ||