Changes between Version 1 and Version 2 of FlexibleAssignToPlugin
- Timestamp:
- Oct 17, 2007, 1:12:57 PM (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
FlexibleAssignToPlugin
v1 v2 1 = FlexibleAssignTo = 2 3 == Description == 4 1 [[TOC]] 5 2 == What is it? == 6 FlexibleAssignTo finally gives long-suffering Trac admins a way to3 !FlexibleAssignTo finally gives long-suffering Trac admins a way to 7 4 easily customize the 'assign to' field on tickets. It provides several 8 5 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) 16 13 17 * 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.14 * 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. 18 15 19 16 * 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). 22 19 23 * FlexibleAssignTo processing can be selectively disabled for individual workflow states20 * !FlexibleAssignTo processing can be selectively disabled for individual workflow states 24 21 25 22 * Example plugin implementation included (!SampleValidOwnerProvider.py)