[rt-users] How to add mandatory custom field to "quick ticket creation" area

[Adam Smith]

All users I have tested with can modify the field values either on  
create or after create, but the problem is that if they choose not to  
set any value at all upon create, RT is letting this through.  It  
should not.  My assumption is based on the fact that they can modify  
the field values later, that for some reason RT isn't enforcing this  
validation on create.


Any ideas?

On 3 Oct 2008, at 18:08, Kenneth Crocker wrote:

> Adam,
>
>
> 	Question; are ALL users not able to see/modify this field or just  
> unprivileged users?
>
>
> Kenn
> LBNL
>
> On 10/3/2008 9:48 AM, Adam Smith wrote:
>> On 3 Oct 2008, at 17:43, Kenneth Crocker wrote:
>>> Adam,
>>>
>>>    Assuming you are talking about a "Ticket" Custom Field, I have  
>>> to ask if you:
>>>
>>> 1) Applied the CF to a Queue and
>> I have
>>> 2) Set the CF rights for the Groups that will be using the queue  
>>> where the Ticket CF is applied (ie. "SeeCustomField" and  
>>> "ModifyCustomField").
>> The Everyone group has the ability to both see and modify this field.
>>>    "AssignCustomFields" does not necessarily let someone SEE or  
>>> Modify the CF in a ticket.
>>>    We use 3.6.4 and we have over 25 Custom Fields used in various  
>>> combinations by various Queues and we do not have nay problem. I  
>>> would have to know how ALL you privileges (Global, Queues, CF's/ 
>>> Groups) have been set in order to persue this further. Hope this  
>>> helps.
>> I am making changes to an existing installation and the permissions  
>> are all very open.  There are a number of groups but one company- 
>> level one as well which has fairly open privileges.
>> Once a ticket is created (or indeed, on create) the user is able to  
>> add values or modify values on this field, which tends to indicate  
>> that they have the appropriate permission.  It just seems as though  
>> RT is ignoring the fact that I've set "Mandatory"...
>> Thanks for your help :)




-- 
Adam Smith