[rt-users] Re: CustomField shared between Tickets, Groups, Users, Etc

[falz]

On 8/22/05, falz <darkfalz at gmail.com> wrote:
> On 8/22/05, falz <darkfalz at gmail.com> wrote:
> > It appears that when you create a custom field, it can only exist in
> > one of the following: Tickets, Groups, Users, Ticket Transactions,
> > (and in my case Assets, since I'm using the AT addon)
> >
> > I have a customfield called "Customer" that is an export from another
> > database that contains a customer name and a unique serial #. I use
> > this for "Tickets" right now, and would like to use it for "Assets" as
> > well. Until this point, I didn't realize that CustomFields are for one
> > thing or the other. The way the database appears to be laid out, the
> > CustomField column in CustomFieldValues permits only a single #
> > assigned to it, so I can't "share".
> >
> > Anyone know of a way to get this working without duplicating my
> > database import to have the same data, but a CustomField column entry
> > # for both CustomFields?
> >
> Another note, it appears that if the LookupType column in the
> CustomFields database supported more than one type, this would work. I
> haven't attempted this yet. Has anyone else? :)


No one's had the need to share a custom field between items such as
Tickets, Assets, Groups, Users? Is anyone else using an import from
another database as an identifier in some way?

If this is not possible, can RT call to an external database for a
customfield, isntead of reading from its local CustomFieldValues
table?

--falz