Changes between Version 20 and Version 21 of FeatureRequests

Timestamp:

Jan 25, 2007, 2:51:10 AM (17 years ago)

Author:

anonymous

Comment:

More features. Is this

FeatureRequests

@@ -16 +16 @@
  * Answer by email to email notification gets stored as a comment, attached files as well (see roundup issue tracker [http://roundup.sourceforge.net])
  * Ability to subscribe for email notification of changes to a specific wiki page.
- * Tickets should get 'time planned' and 'time spent on ticket' fields, in man hours. Those values should be consulted for a milestone's progress bar. That feature would enable users to use the ticket/milestone system for planning development processes.
+ * Tickets should get 'time planned' and 'time spent on ticket' fields, in man hours. Those values should be consulted for a milestone's progress bar. That feature would enable users to use the ticket/milestone system for planning development processes. (seems like there are plugins & custom fields for this kind of thing)
  * Allow users to switch between wiki markup edit mode and a WysiWyg editor such as fckeditor ala seedwiki (http://www.seedwiki.com/wiki/online_teaching_and_learning_issues/online_teaching_and_learning_issues.cfm?wpid=&edit=yes&editorchoice=3)
- * Add additional fields to ticket: steps to reproduce, expected results, observed results (see (http://www.joelonsoftware.com/articles/fog0000000029.html)) (one comment: These could just go in additional comments, no more fields please.)
+ * Add additional fields to ticket: steps to reproduce, expected results, observed results (see (http://www.joelonsoftware.com/articles/fog0000000029.html)) 
+  * (one comment: These could just go in additional comments, no more fields please.)
+  * WikiMarkup in CustomFields
+  * RequiredFields too. Would be nice to require developers to note the svn changelists for items transitioned to QA. 
  * Clarify the Trac ticket system for use as a TODO checklist, instead of a "bug tracker."  eg, "normal" severity is currently used for TODO items.
  * provide closed tickets by milestone RELEASE file (xml or otherwise
  * index the source code to make it available to Trac searches
  * Auto-generated  CHANGELOG for milestones
+ * WatchAPage for email alerts when a page changes. 
+ * SendEmailToUser from a ticket. 
+ * CommentsInTimeline would be great to get RSS for comments to tickets. 
+
+ *