[Rt-devel] [rt-users] Ticket web form: Custom Field display configuration

[Rémi]

hi all,

I think there is a bug with this feature and the "Category" CF
generated with the script RT/etc/upgrade/split-out-cf-categories ,
I use the script to split out some CFs, and then I cannot move up the
generated "category" CF in Queue -> Ticket Custom Fields , a message
said "cannot move CF, already to the top" but it was not on the top

I see the generated "category" CF has the same SortOrder value as the
"base" CF in the table ObjectCustomFields, changing this value by hand
resolve my problem

ps :I used the script include with RT 3.8.8

regards,

Rémi

2010/11/30 Joanne Keown <Joanne.Keown at coloradogroup.com.au>:
> Thanks Kevin for your pointer - I've found this feature (a bit hidden though, I must say) and this has done the trick.
>
> Kind regards
> Jo
>
> Joanne Keown, MBusAdmin(Mgt), PNA
> IS Business Analyst
> Colorado Group Ltd
> 100 Melbourne Street
> South Brisbane  QLD   4101
> Ph:    +61  7 3877 3399
> Mobile:   0402 697 351
> Fax: +61 7 3877 3289
> Email: joanne.keown at coloradogroup.com.au
> Join FUSION now and get special member rewards at 5 of Australia's leading fashion brands.
>
> www.fusioncard.com.au
>
>
>
>
> -----Original Message-----
> From: rt-users-bounces at lists.bestpractical.com [mailto:rt-users-bounces at lists.bestpractical.com] On Behalf Of Kevin Falcone
> Sent: Wednesday, 1 December 2010 12:53 AM
> To: rt-users at lists.bestpractical.com
> Subject: Re: [rt-users] Ticket web form: Custom Field display configuration
>
> On Tue, Nov 30, 2010 at 12:14:00PM +0100, Rémi wrote:
>> I just have a look to the background of customfields display,
>> and I can see there is a "SortOrder" field in the tables CustomFields
>> and ObjectCustomFields and it seems that the one in ObjectCustomFields
>> table is really affecting the display order.
>>
>> I can't see where this value can be modified in the RT interface, I
>> test it directly in the database.
>
> You can change this in Queue -> Ticket Custom Fields
>
> Changing things in the database is rarely the correct way to fix
> something like this
>
> -kevin
>