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
13 ----------------------------------------
15 ----------------------------------------
17 - Make summary field longer
19 ----------------------------------------
21 ----------------------------------------
22 - Help bubbles detailing each field
24 ###############################################################################
27 ----------------------------------------
29 ----------------------------------------
30 - Switch to power-programming classes
31 - Language independence
33 ----------------------------------------
35 ----------------------------------------
36 - Phrase tools for import/export/translating
38 ----------------------------------------
40 ----------------------------------------
41 - Email-based reporting
42 - "Flags" for bugs and attachments --> mimic Bugzilla
43 - QuickTriage feature --> uses AJAX
44 - Auto action comments should be able to have dynamic text (i.e. variables in the comment)
46 ----------------------------------------
48 ----------------------------------------
49 - Have a favourite queries list
50 - Mass updates and deletes
51 - Search attachment filenames and descriptions
52 - Allow multi selections for all select options
53 - Key words should be applied to custom text fields so they won't have their own text box
55 ----------------------------------------
57 ----------------------------------------
58 - User-selectable column displays
59 - User-selectable row colours (as opposed to forced admin-based ones, use default if not set)
60 - CC/Email notifications
61 - When displaying a bug, show dependency and relation trees