Bugzilla Fixup: Difference between revisions

Jump to navigation Jump to search
Update to show what was done as part of Stage 2
(Update to show what was done as part of Stage 2)
Line 18: Line 18:
** Re-sorts on client side should be done via JS
** 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>
** 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>
* Stage 2
* <strike>Stage 2
** Backport https://bugzilla.mozilla.org/buglist.cgi?bug_id=174085,329701,405476 from 3.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=251556 (regression flags)
Line 24: Line 24:
** Way to tell if a patch has been landed, and if so, where?
** 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)
** 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)
** Solidify the XML API so a new UI can be build (kinda a P2, but needs to get started for long term progress)
** 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)
** 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)
** Reports - can't edit reports, have to share on create, one shot to create report - can't edit, can't delete - just improve this
** Multi-state flag (nominate, blocks release, blocks final, arbitrary), deprecate options, one flag per branch  
** Multi-state flag (nominate, blocks release, blocks final, arbitrary), deprecate options, one flag per branch  
** Replace the barely functional branch-tracking flags ({{bug|336790}})
** Back-port 3.2 addition of flags and groups to quicksearch</strike>
** Back-port 3.2 addition of flags and groups to quicksearch
* Stage 3
* 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)  
** 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.  
** In bugmail, include a quick header which includes (customizable): flags, any patch status, priority, component, and bug assignee.  
Line 36: Line 34:
** New UI for bugzilla using the API
** New UI for bugzilla using the API
** Create user pref for user keybindings
** 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}})


= Suggestions/nominations =
= Suggestions/nominations =
canmove, Confirmed users
345

edits

Navigation menu