Re: [rt-users] Tracking changes to queue structure

2009-11-24 Thread Ken Crocker
Gordon, That's where the comment comes in. Kenn LBNL On 11/23/2009 3:35 PM, gor...@cryologic.com wrote: Thanks Ken, I use this feature for some fields but others require information specific to a ticket (eg description of product design change). Also, reviewers of historical tickets can

[rt-users] Tracking changes to queue structure

2009-11-23 Thread gordon
RT provides an excellent history log of all activities relating to a ticket. This provides an unchangeable record which auditors love when reviewing tickets. However we occasionally make changes to a queue such as adding a new custom field. This does not get filled in for historical tickets

Re: [rt-users] Tracking changes to queue structure

2009-11-23 Thread Ken Crocker
Gordon, RT has a Bulk Update feature which would allow you to add whatever value to specific Custom Fields on tickets in specific Queues as well as add comments to specific tickets in a queue. By specific, I mean whatever criteria you use for selecting the ticket you want to update. Kenn LBNL

Re: [rt-users] Tracking changes to queue structure

2009-11-23 Thread gordon
Thanks Ken, I use this feature for some fields but others require information specific to a ticket (eg description of product design change). Also, reviewers of historical tickets can still ask the question: why wasn't the field filled in when the ticket was active? Gordon Ken Crocker

Re: [rt-users] Tracking changes to queue structure

2009-11-23 Thread Nick Kartsioukas
On Tue, 24 Nov 2009 10:35:31 +1100, gor...@cryologic.com said: I use this feature for some fields but others require information specific to a ticket (eg description of product design change). Also, reviewers of historical tickets can still ask the question: why wasn't the field filled in

Re: [rt-users] Tracking changes to queue structure

2009-11-23 Thread gordon
Nice idea, I like it! thanks Gordon Nick Kartsioukas wrote: On Tue, 24 Nov 2009 10:35:31 +1100, gor...@cryologic.com said: I use this feature for some fields but others require information specific to a ticket (eg description of product design change). Also, reviewers of historical