I have installed the extension, with help from Rus (Thank You), to require mandatory fields be filled in prior to a response or comment.
Is there a way to enforce this on any update except the queue change?
I have situations where a ticket is created in queue A which has no CF’s and then transferred to queue B which has 1 to many mandatory CF’s.
In order to maintain the integrity of the CF’s value I need to make sure folks are updating.
Yes I have asked, etc. but they just get going so fast they do not always remember.
Thanks
Joe
Joe Kirby , Assistant Vice President, Business Systems
Division of Information Technology (DoIT)
Support Response - http://www.umbc.edu/doit
Administration 627
Office - 410-455-3020
Email - kirby@umbc.edu
I have installed the extension, with help from Rus (Thank You), to require mandatory fields be filled in prior to a response or comment. Is there a way to enforce this on any update except the queue change? I have situations where a ticket is created in queue A which has no CF's and then transferred to queue B which has 1 to many mandatory CF's.� In order to maintain the integrity of the CF's value I need to make sure folks are updating.� Yes I have asked, etc. but they just get going so fast they do not always remember.
What about enforcing to fill those fields at the “resolved” stage?
Easter-eggs Sp�cialiste GNU/Linux
44-46 rue de l’Ouest - 75014 Paris - France - M�tro Gait�
Phone: +33 (0) 1 43 35 00 37 - Fax: +33 (0) 1 43 35 00 76
mailto:elacour@easter-eggs.com - http://www.easter-eggs.com
Message: 2
Date: Mon, 25 Feb 2013 10:29:31 +0100
From: Emmanuel Lacour elacour@easter-eggs.com
To: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] Mandatory Fields enforcement
Message-ID: 20130225092931.GD4867@easter-eggs.com
Content-Type: text/plain; charset=iso-8859-1
I have installed the extension, with help from Rus (Thank You), to require mandatory fields be filled in prior to a response or comment. Is there a way to enforce this on any update except the queue change? I have situations where a ticket is created in queue A which has no CF's and then transferred to queue B which has 1 to many mandatory CF's.? In order to maintain the integrity of the CF's value I need to make sure folks are updating.? Yes I have asked, etc. but they just get going so fast they do not always remember.
What about enforcing to fill those fields at the “resolved” stage?
I have that in place now as an outcome of the Extension for correspondence but I was hoping to have it done much earlier in the process for reporting purposes and also not to slow down the resolution process
Thanks for your post.
Joe