[whups] Re: [cvs] commit: whups admin.php ...

[Mike Baptiste]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Can't wait to check out the new attribute code!  We will definitely use
it.  We also hope to take it one step further along the lines of
something previously mentioned here.

It would be very nice to have a 'turba' attribute type for tickets.  Not
necessarily as part of the new attribute code (don't know - haven't
looked at it yet).  At Duke, all of our people are in a central
Enterprise LDAP directory, so it would be great if we could simply put
in their NetID (the unique key we use) as the 'key' and pull in or at
least link into the data stored in their record (Phone, Office,
department, email, etc, etc).  Not necessarily display it all, but
display some based on config, or display details on mouseover, etc.

We also want to be able to link in an asset record.  Again - in generic
form as a turba object so the backend can be SQL, LDAP, etc.  We'll
probably use LDAP records for assets, but some others might use SQL.
(Way down the line I'm envisioning a Horde package that can handle asset
management with an SQL or LDAP backend, etc.  But that's way off)

So the basic concept is you can configure standard turba objects like
you normally would, including permissions, etc.  Then in whups, you can
configure a turba 'object' (or two or more) for a given ticket type and
in that config you outline which field is the unique key, which
attribuutes/fields you want displayed, and how they are displayed.  Or
maybe just leverage the turba code and maintain the object config in
whusp only - whichever is more appropriate and/or easier.

I think this would provide a great functionality to link into outside
systems at an abstraction level that lets you leverage the stuff already
in Turba.

What do you all think?  Keep it general enough so it can be used for
anything.  Granted you wouldn't necessarily be able to search on this
data, etc.  But it would provide you with a LOT more info when working
on a ticket vs looking it up manually in an external system.

Mike



Robert E. Coyle wrote:

| At least two other people (Mike Baptiste and adam@morrison-ind IIRC) also
| mentioned that they needed ticket attributes.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE93AaJtbf8BjvL+3ERAuhhAKDO2MoCGaib3MO4SxwpwMwULqLGpACgnE3C
a3BAv86907pHIaJhlqKMxNg=
=F316
-----END PGP SIGNATURE-----