|
|
|
Issue Links:
|
Relates
|
|
|
|
This issue has been marked as being related by:
|
|
|
MDLSITE-408 CVS Developer Module: ability to add comment without approving or rejecting
|
|
|
|
|
|
|
|
Suggested changed to CVS admin
1. Create a comprehensive history for each CVS requester and/or user. Show: initial request, all comments from user and admins, all status changes.
1a Create a simple log (or list) of rejected users - this list may or may not be part of the main log but it should be easy to find a list of all rejectees (perhaps using date ranges?) i.e. this info shouldn't be buried in a way that makes difficult to use.
2. Give admin the ability to send the user a message and receive a reply (include in the log).
3. Create a new section in list for ex-developers. Perhaps when "none" is entered into the directory field the user is "deactivated" and moved the to new section at the bottom of the list.
4. Add counts to each table section: new, update, approved, retired.
|
|
Description
|
Suggested changed to CVS admin
1. Create a comprehensive history for each CVS requester and/or user. Show: initial request, all comments from user and admins, all status changes.
1a Create a simple log (or list) of rejected users - this list may or may not be part of the main log but it should be easy to find a list of all rejectees (perhaps using date ranges?) i.e. this info shouldn't be buried in a way that makes difficult to use.
2. Give admin the ability to send the user a message and receive a reply (include in the log).
3. Create a new section in list for ex-developers. Perhaps when "none" is entered into the directory field the user is "deactivated" and moved the to new section at the bottom of the list.
4. Add counts to each table section: new, update, approved, retired.
|
Show » |
made changes - 07/Apr/08 12:30 PM
| Field |
Original Value |
New Value |
|
Description
|
Suggested changed to CVS admin
1. Create a comprehensive history for each CVS requester and/or user. Show: initial request, all comments from user and admins, all status changes.
2. Give admin the ability to send the user a message and receive a reply (include in the log).
3. Create a new section in list for ex-developers. Perhaps when "none" is entered into the directory field the user is "deactivated" and moved the to new section at the bottom of the list.
|
Suggested changed to CVS admin
1. Create a comprehensive history for each CVS requester and/or user. Show: initial request, all comments from user and admins, all status changes.
2. Give admin the ability to send the user a message and receive a reply (include in the log).
3. Create a new section in list for ex-developers. Perhaps when "none" is entered into the directory field the user is "deactivated" and moved the to new section at the bottom of the list.
4. Add counts to each table section: new, update, approved, retired.
|
made changes - 07/Apr/08 03:39 PM
|
Link
|
|
This issue has been marked as being related by MDLSITE-408
[ MDLSITE-408
]
|
made changes - 14/Apr/08 04:41 PM
|
Description
|
Suggested changed to CVS admin
1. Create a comprehensive history for each CVS requester and/or user. Show: initial request, all comments from user and admins, all status changes.
2. Give admin the ability to send the user a message and receive a reply (include in the log).
3. Create a new section in list for ex-developers. Perhaps when "none" is entered into the directory field the user is "deactivated" and moved the to new section at the bottom of the list.
4. Add counts to each table section: new, update, approved, retired.
|
Suggested changed to CVS admin
1. Create a comprehensive history for each CVS requester and/or user. Show: initial request, all comments from user and admins, all status changes.
1a Create a simple log (or list) of rejected users - this list may or may not be part of the main log but it should be easy to find a list of all rejectees (perhaps using date ranges?) i.e. this info shouldn't be buried in a way that makes difficult to use.
2. Give admin the ability to send the user a message and receive a reply (include in the log).
3. Create a new section in list for ex-developers. Perhaps when "none" is entered into the directory field the user is "deactivated" and moved the to new section at the bottom of the list.
4. Add counts to each table section: new, update, approved, retired.
|
|