Thanks, Chris!
I appreciate the detailed response and suggestions
I suspect you are quite right and for at least some of the custom fields, your
way would be a much better/easier solution!
To be honest, I don't think I had considered (or even knew about?) being able
to control custom field perm
Am 02.06.2014 22:46, schrieb Parish, Brent:
> We have this same problem here.
> If you don't want to wait for the feature request to be implemented, here is
> one way around it:
>
> I ended up creating a second set (copy) of the custom fields.
> I named them the same thing, but with an underscor
om: rt-users [mailto:rt-users-boun...@lists.bestpractical.com] On Behalf Of
Emmanuel Lacour
Sent: Monday, June 02, 2014 9:21 AM
To: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] creating tickets with CF values without
ModifyCustomField right
On Mon, Jun 02, 2014 at 02:44:14PM +0200,
On Mon, Jun 02, 2014 at 02:44:14PM +0200, Christian Loos wrote:
> Hi,
>
> is it possible to create tickets with CF values for users that don't
> have the ModifyCustomField right?
> Currently if fails with "Permission Denied" in
> RT::CustomField->AddValueForObject().
>
> We have some users that u
Hi,
is it possible to create tickets with CF values for users that don't
have the ModifyCustomField right?
Currently if fails with "Permission Denied" in
RT::CustomField->AddValueForObject().
We have some users that use the RT WebUI to create tickets and must
enter on ticket create some CF values
