Joop,
It will take a couple of months, because I'm in the middle of writing
some code in CLI/SQL to convert about 7,500 table records from another
ticketing system in Oracle into RT. However, when I DO get to this, I'm
hoping, first of all, to get my technical support groups to agree
Kenneth Crocker wrote:
Stephen, thanks a bunch for your help. We are getting bigger here by
the month. I just added 25 more tech support queues AND they are now
wanting me to use the CF URL link ability to tie in a Resolve to
linking to version control. Kool, huh? that should a a LOT
Kenn,
Are you seeing this problem (custom fields not in the order you
specify) on ticket display basics screens too? Are you using
Oracle, and what version of DBIx::SearchBuilder do you have?
After a recent upgrade of DBIx::SearchBuilder, we are seeing ticket
custom fields in the wrong
Stephen,
Yes indeed. We use Oracle 9 in Prod at the moment, but will be on 10
soon. I just upgraded my Dev to 3.6.6 so I think my SearchBuiler is at
1.53. In Prod we are at 3.6.4 and 1.49 respectively. Prod doesn't seem
to show this problem. I also noticed that in DEV, the CF's are
Hi Kenn,
I don't have the ultimate solution but I changed the behavior in that
way, that there will be one column of custom fields only instead of two.
This makes the look of RT much better. You just need to edit
/opt/rt3/share/html/Ticket/Elements/EditCustomFields (copy it into local
of
Benjamin,
I plugged in your code right at the top, just below the last comment
and in front of the init and got the following error:
Error during compilation of
/apps/rt/rt-3.6.6/local/html/Elements/EditCustomField:
Global symbol $CustomFields requires explicit package name at
