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.

SVN: $Id$

###############################################################################
BUGTRACK 1.0

----------------------------------------
  ADMINISTRATION
----------------------------------------
- PCV descriptions
- Admin auto-actions
- Custom bug fields
- Put either inline admin help or a "what this does" description on each of the widget pages
- Ability to set default templates in the description field
- Update all $admin->error('-1') to something useful

----------------------------------------
  GENERAL USER END
----------------------------------------
- New style
- Language independence
- Help page on how to report and what each field does
- Make summary field longer
- User-selectable column displays
- User-selectable row colours (as opposed to forced admin-based ones, use default if not set)
- When displaying a bug, show a list of bugs that have been marked duplicate
- WHen displaying a bug, show dependency and relation trees
- Error message improvements

----------------------------------------
  BUG REPORTING/EDITING
----------------------------------------
- Custom bug fields
- Default templates in the description field
- Help bubbles detailing each field
- Bug logging/history

###############################################################################
BUGTRACK 1.1

----------------------------------------
  CORE SYSTEM CHANGES
----------------------------------------
- Switch to power-programming classes

----------------------------------------
  BUG REPORTING/EDITING
----------------------------------------
- Email-based reporting
- "Flags" for bugs and attachments --> mimic Bugzilla

----------------------------------------
  SEARCHING
----------------------------------------
- Have a favourite queries list
- Mass updates and deletes