1 THIS IS THE TO-DO LIST FOR BUGTRACK 1.0 AND 1.1. BASE FEATURES SHOULD BE PLACED IN 1.0 WHILE LARGE EXTENSIONS AND ENHANCEMENTS SHOULD BE PLACED IN 1.1.
5 ###############################################################################
8 ----------------------------------------
10 ----------------------------------------
11 - Put either inline admin help or a "what this does" description on each of the widget pages
12 - Phrase tools for import/export/translating
14 ----------------------------------------
16 ----------------------------------------
18 - Language independence
19 - Make summary field longer
20 - Make it so that you can modify bug fields on showreport.php
22 ----------------------------------------
24 ----------------------------------------
25 - Help bubbles detailing each field
27 ###############################################################################
30 ----------------------------------------
32 ----------------------------------------
33 - Switch to power-programming classes
35 ----------------------------------------
37 ----------------------------------------
38 - Email-based reporting
39 - "Flags" for bugs and attachments --> mimic Bugzilla
40 - QuickTriage feature --> uses AJAX
41 - Auto action comments should be able to have dynamic text (i.e. variables in the comment)
43 ----------------------------------------
45 ----------------------------------------
46 - Have a favourite queries list
47 - Mass updates and deletes
48 - Search attachment filenames and descriptions
49 - Allow multi selections for all select options
50 - Key words should be applied to custom text fields so they won't have their own text box
52 ----------------------------------------
54 ----------------------------------------
55 - User-selectable column displays
56 - User-selectable row colours (as opposed to forced admin-based ones, use default if not set)
57 - CC/Email notifications
58 - When displaying a bug, show dependency and relation trees