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 - When displaying a bug, show dependency and relation trees
21 - Make it so that you can modify bug fields on showreport.php
23 ----------------------------------------
25 ----------------------------------------
26 - Help bubbles detailing each field
28 ###############################################################################
31 ----------------------------------------
33 ----------------------------------------
34 - Switch to power-programming classes
36 ----------------------------------------
38 ----------------------------------------
39 - Email-based reporting
40 - "Flags" for bugs and attachments --> mimic Bugzilla
41 - QuickTriage feature --> uses AJAX
42 - Auto action comments should be able to have dynamic text (i.e. variables in the comment)
44 ----------------------------------------
46 ----------------------------------------
47 - Have a favourite queries list
48 - Mass updates and deletes
49 - Search attachment filenames and descriptions
50 - Allow multi selections for all select options
51 - Key words should be applied to custom text fields so they won't have their own text box
53 ----------------------------------------
55 ----------------------------------------
56 - User-selectable column displays
57 - User-selectable row colours (as opposed to forced admin-based ones, use default if not set)
58 - CC/Email notifications