<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN">
<html><body>
<p>Same situation here, use this plugin http://blog.bestpractical.com/2013/03/new-rt-extension-for-making-fields-mandatory-on-status-transitions.html (https://metacpan.org/pod/RT::Extension::MandatoryOnTransition)</p>
<p>Set Custom Fields to not mandatory on creating new ticket, then set plugin options to force mandatory CF on any or specific transaction, change of status (ex, for closed ticket - fields have to be mandatory)</p>
<p>Enjoy!</p>
<p> </p>
<p>W dniu 2014-02-04 11:07, Paul Stead napisał(a):</p>
<blockquote type="cite" style="padding-left:5px; border-left:#1010ff 2px solid; margin-left:5px; width:100%"><!-- html ignored --><!-- head ignored --><!-- meta ignored --><span style="font-family: Helvetica,Arial,sans-serif;">Hello,<br /><br /> Running RT 4.0.17 on Debian.<br /><br /> We're trying to use RT across the company as our main ticketing system. This requires other departments to raise tickets into our queue.<br /><br /> We have two mandatory ticket custom fields in this queue for us to internally categorise tickets. <br /> Our standard users do not have rights to "</span>View custom field values" or "Modify custom field values" and indeed cannot see or set these fields in the Create Ticket view.<br /><br /> When the user attempts to raise the ticket, RT seems to be checking for the validity of these custom fields, even though the user has no ability to set them.<br /><br /> Raising via email works as expected, but our users are used to the RT interface and prefer to raise this way.<br /><br /> Is this expected behaviour? How might I work around this? <br /><br /> Paul<br /> --<br /> Paul Stead<br /> Systems Engineer, Zen Internet<br /> T: 01706 902009</blockquote>
<p> </p>
<div>
<pre>-- <br />Bartosz Maciejewski
IT Administrator
Agri Plus Sp. z o.o.
ul.Marcelińska 92/94
60-324 Poznań
tel: 061 665 79 77
gsm: 666 866 549
Please consider the environment before printing this email.</pre>
</div>
</body></html>