> As an example, when handling a change control, we have to document the > servers >(want a linked asset), the software, Maybe http://code.google.com/p/asset-tracker-4rt/?
> the person handling the change, the time and date of the change, the change >description, the change procedure (usually an attachment, but, could be just >a few >lines of text for an easy one..), Those tidbits all sound like part of a normal transaction in RT, not free form info, to me. >the backout procedure, testing data, and any procedures modifed (separate >linked >ticket), along with a few more details, and a raft of signatures.... This >is currently >done mostly manually, via paper forms. This mostly just imposing a structure on how you use the tool I think? _______________________________________________ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [email protected] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
