Bernard, A couple of questions:
1) is this a GLOBAL CF? If not, it needs to be "Applied" to the Queues where it should reside. 2) Did you grant rights for this CF by Group or by Queue? It makes a difference. I can create all the Global or Queue-level CF's I want, but if I don't grant the rights to "see" it, no one will. The same applies for modifying the CF. Also, I would NEVER modify the Custom Field Tables (there are 4 of them) manually unless you make sure you keep them "insync". That also includes the ACL table which maintains the rights to see & modify & admin these Custom Fields. You could easily create a situation that will be bvery messy to correct. Kenn LBNL On Wed, Mar 2, 2011 at 2:20 AM, Bernard McCormack <[email protected]>wrote: > I’m creating a new user custom field in rt 3.8.8 and I’m not seeing in the > ui till I manually update table `rt3`.`ObjectCustomFields` with the > values(in seeing in the ui I mean on the ticket /ui It does appear on the > edit custom fields page under config). This is only occurring on my > production db. When I point my dev box at the production db I see the same > issue. I have given the user admin access to the db and it is still > failing. Nothing is in the rt logs other than debug messages from External > auth: > > [Wed Mar 2 10:13:28 2011] [debug]: Reloading RT::User to work around a bug > in RT-3.8.0 and RT-3.8.1 > (/opt/rt3/local/plugins/RT-Authen-ExternalAuth/html/Callbacks/ExternalAuth/autohandler/Auth:14) > > > > > > . The rt siteconfig is set to debug and still I’m seeing nothing. > > > > --Bernard. >
