Changes between Version 1 and Version 2 of FlexibleAssignToPlugin

Timestamp:

Oct 17, 2007, 1:12:57 PM (17 years ago)

Author:

Morris

Comment:

--

FlexibleAssignToPlugin

@@ -1 @@
-= FlexibleAssignTo =
-
-== Description ==
-
+[[TOC]]
 == What is it? ==
-FlexibleAssignTo finally gives long-suffering Trac admins a way to 
+!FlexibleAssignTo finally gives long-suffering Trac admins a way to 
 easily customize the 'assign to' field on tickets.  It provides several 
 base classes for you to override and implement your own methods for
@@ -15 +12 @@
  * provides !SimpleUser base class and helper methods (getlist, getbool) to streamline implementation of your IValidOwnerProvider component(s)
 
- * data-source agnostic -- FlexibleAssignTo abstracts the nastiness of building a customized 'assign to' select box.  All your custom code has to do is decide what users are valid for a particular state and then return them.
+ * data-source agnostic -- !FlexibleAssignTo abstracts the nastiness of building a customized 'assign to' select box.  All your custom code has to do is decide what users are valid for a particular state and then return them.
 
  * optional 'ensure_user_data' capability so that users who appear as valid 'assign to' targets get their key data (username, fullname, email) stored in the Trac session_attribute table.  The motivation for this was so notification emails could be sent to these users even if they've never logged in and set their preferences.
@@ -21 +18 @@
  * optional get_known_users() replacement that changes Trac's 'known users' concept such that users' name & email data is retrieved from the session_attribute table (designed to work in concert with the 'ensure_user_data' capability).
 
- * FlexibleAssignTo processing can be selectively disabled for individual workflow states
+ * !FlexibleAssignTo processing can be selectively disabled for individual workflow states
 
  * Example plugin implementation included (!SampleValidOwnerProvider.py)