This all make sense but it still doesn't seem to actually answer my
question, which is all about your step 14. Because setting custom fields can
happen at ticket *creation*, it's not
obvious to me that one should need a right called *modify*, but this
appears to be the case,
and what I was trying
Jarred,
Not exactly. Let me see if I can walk thru a sequence of events and
maybe that will help. Trust me, it wasn't easy for me to understand at
first either.
1. Queue 'X' is created.
2. Queue 'Y' is created.
3. Group 'X-Support' is created.
4. Group '
On Thu, Aug 21, 2008 at 13:24, Kenneth Crocker <[EMAIL PROTECTED]> wrote:
> Jerrad,
>
>
>Actually, the "ModifyCustomField" privilege doesn't have anything to
> do with creating tickets. When a ticket is created, an
> OBJECTCUSTOMFIELDVALUES table record (where the value of the CF for that
Jerrad,
Actually, the "ModifyCustomField" privilege doesn't have anything to do
with creating tickets. When a ticket is created, an
OBJECTCUSTOMFIELDVALUES table record (where the value of the CF for that
ticket is held) is created automatically for that ticket for each custom
field a
Is it normal that this should require the ModifyCustomField right? Because
it doesn't seem at all intuitive to me,
nor does the documentation clearly indicate that this should be the case.
Alas, I've lost quite a bit of time due
to this :-/
--
Cambridge Energy Alliance: Save money & the planet
__
