[rt-users] Change control

[Ken Crocker]

Chuck,

    We are attempting to do just that here at LBNL. The "APPROVAL" setup 
in RT does not seem to create the kind of audit trail we would like. We 
would like a request to keep it's number, that way every stage, from 
approval for work to approval for Acceptance testing to approval for 
installation is in history for the same request numer and therefore 
easier to track. If RT would allow for a few more options in the 
drop-down selection for staus (like "pending approvel", "approved for 
work", "approved for QA", "approved for inplementation"), we could write 
scrips to move a request from  a particular approval  queue to a work 
queue and back to another  approval queue (for QA as an example) and on 
to implemntation. That way queues can be used as steps in a work flow 
and the history of a request remains intact with the same number, going 
from  queue to queue in the workflow.  Well, anyway, that's one idea we 
have.  It may require scrips that modify the status field temporarily 
until the request can be moved to another queue and modify the status 
again. We don't know yet because we are currently in the process of 
playing with this design idea, but at least it is an idea that could 
work, provided RT can handle the change to the status field.

Kenn

Chuck Boeheim wrote:

> Hi Folks,
> Has anyone come up with any good methodologies for change control
> of an RT installation?  Many of the components are database records
> that don't seem amenable to CVS control, scrips and templates as well
> as custom field definitions and queue setups.  We'd like to have a record
> of what changed when and by whom, and be able to reconstruct the
> state of the system or back out a change.  Even an audit record of  what
> changed would be better than nothing, even if it can't be used directly
> for backing out a change.  Has anyone tackled this?
> Best,
> -Chuck Boeheim
> Stanford Linear Accelerator Center
>
>------------------------------------------------------------------------
>
>_______________________________________________
>http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
>
>Community help: http://wiki.bestpractical.com
>Commercial support: sales at bestpractical.com
>
>
>Discover RT's hidden secrets with RT Essentials from O'Reilly Media. 
>Buy a copy at http://rtbook.bestpractical.com
>
>
>We're hiring! Come hack Perl for Best Practical: http://bestpractical.com/about/jobs.html
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20060314/9ed20503/attachment.htm>