= DrawMGT Wish List =
 * '''Requests and Ideas for new DrawMGT Features'''

<<TableOfContents>>

= Major Features =
 * Generic reports

 * Dashboard that displays:
  * '''Revisions''' with workflow steps assigned to me.
  * New/pending/repoened '''tasks''' assigned/delegated to me


= Minor Bugs =

= General =

= Document Related =

 1. Allow changing of document codes, even if a revision file has been uploaded, provided the file uses an internal number.

 1. Add a comment field for each workflow field that has an approval status. This is to allow entry of a comment for approved with comments.

 1. Make entry of a comment required when a revision is rejected

 1. Add approval status over-rulled (for release/versand only?)

 1. '''For NOK & IDP''' (by end 2010-Q1) - Document detail should the list of transmissions in which the document was sent. Including (if possible) the status of their download.

 1. '''For IDP''' - Management of distribution lists of transmission recipients. The list members may be DrawMGT users or external email addresses.

 1. Linking documents to other tasks. Must including a link reason (related, sub-task, etc). Should allow trees of documents and document  dependencies.

 1. Document codes where the first X characters are fixed, and he rest is free.

= Task Related =

 1. --(In Document Detail: When you press the New Comment button, it should copy the classification information from the document to the new task.)--  DONE 2009-11-13  V11.3

 1. Allow entry/update of subscribers when entering a new task

 1. Linking tasks to other tasks. Must including a link reason (related, sub-task, etc). Should allow trees of tasks and task dependencies.

 1. Metadata download of tasks

= History Related =
 * Implement field-level history messages. List before/after for each field that was changed. At least for:
  * Revisions
  * Tasks
 Could be solved generally by database trigger. Apache-PHP connects-disconnects from the database at every request. Therefore the userId should be saved to a small table with the database session id (@@pseudo_thread_id for MySQL) as key at every action, to allow the trigger to determine the user. Small example for using triggers:
 . {{{
create table history ( date date, time time, session_id int, old int, new int );
create trigger tr_upd_comments after update on Comments for each row
  insert into history values( now(), now(), @@pseudo_thread_id, old.projectPhaseId, new.projectPhaseId );

update Comments set projectPhaseId = 8 where commentId = 10;
select * from history;
}}}

 * Implement file versioning for uploaded files (add a version number field to the internal file names?)

= Back-End Tools =
 1. Update app/etc/uploadFile.pl to:
  * handle internal file names
  * handle matching of first 'x' characters of filename against drawing code

 1. Tool up upload comments from a spreadsheet.