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