Locking up Custom Fields

Hello list!!!

I have an RT 3.6.1 installation, and RT works fine for me.

I was hopping someone could help me out on this one:
I have a couple of Custom Fields that must be filled up on the ticket
creation BUT after that, they MUST NOT be changed! In other words, these
specific CF must become read-only, uneditable, locked, disabled or
whatever (since it still shows up on the screen), only after creation.

I’ve tried some javascripting but I’m not getting it. I know I can (as I
already have done this) lock a given CF on the creation page, but not on
the Modify or Jumbo pages.

Hope to hear from you experts soon!!
Thanks a lot!

Mario Gomide

I don’t know about JS or any other previous work on this. However, we
thought about adding ModifyCustomFieldOnCreate right. If you write a
patch, we can include it into the core.On Fri, Jul 3, 2009 at 6:32 PM, Mario Gomidemario.gomide@agricultura.gov.br wrote:

Hello list!!!

I have an RT 3.6.1 installation, and RT works fine for me.

I was hopping someone could help me out on this one:
I have a couple of Custom Fields that must be filled up on the ticket
creation BUT after that, they MUST NOT be changed! In other words, these
specific CF must become read-only, uneditable, locked, disabled or
whatever (since it still shows up on the screen), only after creation.

I’ve tried some javascripting but I’m not getting it. I know I can (as I
already have done this) lock a given CF on the creation page, but not on
the Modify or Jumbo pages.

Hope to hear from you experts soon!!
Thanks a lot!

Mario Gomide


http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.com

Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com

Best regards, Ruslan.