Is there any documentation other than the files in $RTHOME/lib/RT/Actions which
layout the steps required for adding your own scrip actions? I’m looking to add the
following:
when a parent ticket status is changed, all the childrens status is changed
when a message comes in, do some intelligent parsing to ensure the proper
information is included
Also, is there any plan to add arbitrary values to the keyword system? In
otherwords, I’d like to be able to add a keyword “MAC Address” and be able to enter
the MAC address of the system in question for each ticket. This would be a very
handy mechanism since it gives you some ad-hoc easily extensible database
possibilities. Any thoughts on this?
[deleted question about developing scrips, not because it’s not important, but
because I don’t have the energy or hand strength to answer just now]
Also, is there any plan to add arbitrary values to the keyword system? In
otherwords, I’d like to be able to add a keyword “MAC Address” and be able to enter
the MAC address of the system in question for each ticket. This would be a very
handy mechanism since it gives you some ad-hoc easily extensible database
possibilities. Any thoughts on this?
That’s not really doable with the current schema. One of the things under consideration for 2.2 is generic “custom field” support that would allow single and multi-value text-entry fields, as well as the current keyword selects.
autoconf is your friend until it mysteriously stops working, at which
point it is a snarling wolverine attached to your genitals by its teeth
(that said, it’s better than most of the alternatives) – Nathan Mehl