View source for Bugzilla Fixup

We have kicked off a project to improve Bugzilla, specifically to help the Mozilla team be more efficient and effective when using the tool.  In this first stage, we are looking to address low-hanging fruit that can addressed quickly with minimal change.  In later phases we'll address some of the longer term issues.

Please add suggestions under "Suggestions/nominations" along with your name/email.  We'll evaluate the the suggestions and fit it in ASAP based on all feedback and difficulty.
 
* <strike>Stage 1
** Send mail asynchronously - don't block the results page while mail is sending when editing a bug. ({{bug|284184}})
** Add Microsummary feed type (similar to rss) ({{bug|339007}})
** Security fixes
*** {{bug|38862}}  (moved to Stage 2)
** Create way to obsolete or hide past milestones ({{bug|77193}})
** Add reports for (usually for past 7 and 14 days)
*** What people are working on (i.e. if a person has made any change to a bug)
*** What a person has attached/landed (relies on other functionality)
*** What has been checked in (relies on other functionality)
*** What has a blocking flag, but not resolved
*** What's been fixed in the last week (closed "fixed")
*** What's been fixed between releases (closed "fixed")
** Re-sorts on client side should be done via JS
** Fix search clobbering.  If you have two searches in two windows (same instance), the first search will fall out of scope and links won't work.</strike>
* <strike>Stage 2
** Backport https://bugzilla.mozilla.org/buglist.cgi?bug_id=174085,329701,405476 from 3.2
** https://bugzilla.mozilla.org/show_bug.cgi?id=251556 (regression flags)
** https://bugzilla.mozilla.org/show_bug.cgi?id=38862
** Way to tell if a patch has been landed, and if so, where?
** 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)
** Add a column in search results containing patches with current review flags or display more obviously an attachment is a patch.  Also, display the status of a patch (review?/+/-, etc)
** Multi-state flag (nominate, blocks release, blocks final, arbitrary), deprecate options, one flag per branch 
** Back-port 3.2 addition of flags and groups to quicksearch</strike>
* Stage 3
** Solidify the XML API so a new UI can be build (kinda a P2, but needs to get started for long term progress)
** better bug reporting forum (more wizard like) 
** In bugmail, include a quick header which includes (customizable): flags, any patch status, priority, component, and bug assignee. 
** Add a "view source" link to attachments ({{bug|346255}})
** New UI for bugzilla using the API
** Create user pref for user keybindings
** Reports - can't edit reports, have to share on create, one shot to create report - can't edit, can't delete - just improve this 
** Replace the barely functional branch-tracking flags ({{bug|336790}})