BMO/TrackingFlags: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
No edit summary
Line 16: Line 16:
** Searching (BzAPI uses buglist.cgi, so we need to remain compatible there)
** Searching (BzAPI uses buglist.cgi, so we need to remain compatible there)
** We need to ensure real custom fields aren't created with conflicting names
** We need to ensure real custom fields aren't created with conflicting names
=== Non-Goals ===
* The user interface on show_bugs will not change from its current presentation.
* The WebService calls required to update flags will not change from its current implementation.


=== Implementation ===
=== Implementation ===
Line 25: Line 30:
* Add tracking fields to a single x-header in bugmail
* Add tracking fields to a single x-header in bugmail
* Should be able to hook into Search.pm to add the custom functions
* Should be able to hook into Search.pm to add the custom functions
* Identify points in the code which deal with 'active_custom_fields', and add a hook to insert our fields at the same location, or inject the fields _as custom fields_ via the current active_custom_fields hook
* most of these problems should have already been solved when the votes column was moved out of the bugs table to its own extension, copy & paste from that
* most of these problems should have already been solved when the votes column was moved out of the bugs table to its own extension, copy & paste from that
 
=== User Interface ===
 
Details on how the UI portion of the new TrackingFlags extension should be designed and implemented.
 
=== WebService API ===
 
Not applicable for first release but an API for adding/removing/editing of tracking flags
via WebService API is planned for future iterations.


=== Database Schema ===
=== Database Schema ===
Confirmed users
1,198

edits

Navigation menu