Account confirmers, Anti-spam team, Confirmed users, Bureaucrats and Sysops emeriti
4,925
edits
BugzillaImprovements: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 7: | Line 7: | ||
== UI == | == UI == | ||
=== Simpler Layout === | === Simpler Bug Layout === | ||
Collapse all the non-required and less-frequently used fields by default. This would simplify the layout of bug reports and make it less daunting for new participants. Allow user prefs to control what gets expanded and collapsed by default for each user. More familiar, easier for new users, streamline navigation. -- chofmann | Collapse all the non-required and less-frequently used fields by default. This would simplify the layout of bug reports and make it less daunting for new participants. Allow user prefs to control what gets expanded and collapsed by default for each user. More familiar, easier for new users, streamline navigation. -- chofmann | ||
| Line 13: | Line 13: | ||
* {{bug|373418}} | * {{bug|373418}} | ||
* Note that we are unlikely to add a user preference for this, but we might remember the shown/hidden state in a cookie. -mkanat | * Note that we are unlikely to add a user preference for this, but we might remember the shown/hidden state in a cookie. -mkanat | ||
=== Text Area Visible On Filing === | === Text Area Visible On Filing === | ||
| Line 24: | Line 18: | ||
When I'm filing a bug, the text area in which I am to describe the bug should be above the fold. Everything else (including the component it's in) is subsidiary to the bug description itself, and should be farther down (or invisible -- why do I care who the default CC: is? why would I ever change the QA contact?) -- shaver | When I'm filing a bug, the text area in which I am to describe the bug should be above the fold. Everything else (including the component it's in) is subsidiary to the bug description itself, and should be farther down (or invisible -- why do I care who the default CC: is? why would I ever change the QA contact?) -- shaver | ||
* Essentially fixed in Bugzilla 3.4, because the bug entry page is simpler by default. | * Essentially fixed in Bugzilla 3.4, because the bug entry page is simpler by default. -- mkanat | ||
** Not if your screen is 1024x768 -- gerv. | |||
=== Fix Mid-Air Collisions === | === Fix Mid-Air Collisions === | ||
| Line 38: | Line 33: | ||
* [https://bugzilla.mozilla.org/show_bug.cgi?id=395970 Bug 395970] - mid-air collision pages cry wolf. | * [https://bugzilla.mozilla.org/show_bug.cgi?id=395970 Bug 395970] - mid-air collision pages cry wolf. | ||
* Note that this is somewhat difficult and unlikely to happen in any near-term Bugzilla release. -mkanat | * Note that this is somewhat difficult and unlikely to happen in any near-term Bugzilla release. -- mkanat | ||
** mkanat: can you point me at any technical analysis which has been done on the problem? -- gerv | |||
=== Historical Queries === | === Historical Queries === | ||
| Line 58: | Line 54: | ||
I guess that finding out a better way to have "fixed here, but needs fixing somewhere else" would be cool, and support for that in queries. -- axel (endorsed by bsmedberg) | I guess that finding out a better way to have "fixed here, but needs fixing somewhere else" would be cool, and support for that in queries. -- axel (endorsed by bsmedberg) | ||
* There is an existing custom feature on b.m.o., but it is considered inadequate. | |||
* [https://bugzilla.mozilla.org/show_bug.cgi?id=bz-branch Bug 55970] - Bugzilla needs to deal better with branches. | * [https://bugzilla.mozilla.org/show_bug.cgi?id=bz-branch Bug 55970] - Bugzilla needs to deal better with branches. | ||
| Line 169: | Line 166: | ||
* A JSON API already exists; need to assess completeness and level of documentation. "Bugzilla 3.6 will have a JSON-RPC API that duplicates the XML-RPC API." -- mkanat. | * A JSON API already exists; need to assess completeness and level of documentation. "Bugzilla 3.6 will have a JSON-RPC API that duplicates the XML-RPC API." -- mkanat. | ||
Note that in order for this to be REST, Bugzilla has to move to Catalyst, a far-reaching rearchitecture that is in the Bugzilla 4.0 or 4.0+ timeframe. JSON-RPC will exist in Bugzilla 3.6, though. | Note that in order for this to be REST, Bugzilla has to move to Catalyst, a far-reaching rearchitecture that is in the Bugzilla 4.0 or 4.0+ timeframe. JSON-RPC will exist in Bugzilla 3.6, though. -- mkanat | ||
Access-Control-Allow-Origin header support for cross-site XML-RPC - asutherland. | Access-Control-Allow-Origin header support for cross-site XML-RPC - asutherland. | ||
=== Bounce Tracking === | === Bounce Tracking === | ||
| Line 273: | Line 258: | ||
* Can't put an alias in a bookmarkable template. | * Can't put an alias in a bookmarkable template. | ||
= Already Implemented = | |||
=== Server-Side Hooks === | |||
Server-side hooks for basically every action, so that f.e. I could write something that did component watching the way I want without having to even discuss it with upstream, let alone make it sufficiently general to be accepted. -- shaver | |||
* These already exist: http://www.bugzilla.org/docs/tip/en/html/api/Bugzilla/Hook.html -- more can be added as requested; hooks are only added that have use cases. Some rearchitecture is required before we can add hooks to performance-critical areas. (Can't find the bug, right now.) -mkanat | |||
=== Shorter Query URLs === | |||
Shorter query URLs by default. -- axel | |||
* Already implemented in Bugzilla 3.4. | |||