BugzillaImprovements: Difference between revisions

Jump to navigation Jump to search
no edit summary
(Add chofmann, reorganize)
No edit summary
Line 35: Line 35:


Ability to orphan components/bugs/flags/etc. without a ton of noise. I should be able to make "fixed1.4.1" never show up in the keyword autocomplete without having to do a pile of bug-munging. -- shaver
Ability to orphan components/bugs/flags/etc. without a ton of noise. I should be able to make "fixed1.4.1" never show up in the keyword autocomplete without having to do a pile of bug-munging. -- shaver
=== JavaScript Autocomplete ===
I would like to see someone finish (or rewrite) the patch I attached to  - JavaScript autocomplete for review request field. For bonus points, the same backend code should be used anywhere else that you currently enter someone's bugmail in the UI. I waste an awful lot of time guessing at people's bugmail. -- ted
* [https://bugzilla.mozilla.org/show_bug.cgi?id=386600 Bug 386600] - JavaScript autocomplete for review request field (patch, July 2007)
=== Multiple Statuses/Resolutions ===
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
=== Nicer Graphs ===
Nicer graphs would be good. -- dtownsend
== Accounts ==
=== Hide from autocomplete ===
Relatedly, people should be able to hide their accounts from
auto-completion or partial matching. -- shaver


== Server ==
== Server ==
Line 41: Line 62:


A full REST+JSON API, so that anything currently possible through the bugzilla web UI (read or write) can be done through another program on another server. -- shaver
A full REST+JSON API, so that anything currently possible through the bugzilla web UI (read or write) can be done through another program on another server. -- shaver
Including chart data. -- dtownsend


=== Server-Side Hooks ===
=== 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
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
=== Shorter Query URLs ===
Shorter query URLs by default. -- axel
=== Bounce Tracking ===
Bug 209181 will save lots of time when processing a lot of bugs and you need to know if reporter mail has not bounced. -- Nikolay Shopik
* [https://bugzilla.mozilla.org/show_bug.cgi?id=209181 bug 209181]


== Speed ==
== Speed ==
Line 54: Line 87:
=== Caching ===
=== Caching ===


Intelligent caching of API and web-UI results, based on modification time for bugs; "generate on change" via the server side hooks would be a DIY option, certainly. -- shaver
Intelligent caching of API and web-UI results, based on modification time for bugs; "generate on change" via the server side hooks would be a DIY option, certainly. -- shaver. Endorsed by axel.




Account confirmers, Anti-spam team, Confirmed users, Bureaucrats and Sysops emeriti
4,925

edits

Navigation menu