After writing a really cool system that allows our RT users to select
from a list of “external source” they want their ticket/reply/comment
posted to (we have a number of “status page” sites), and working up the
code to make that work… And spending a few hours with a Scrip that
should be working fine, I finally noticed in the wiki that “Note: as of
3.6.1, per-transaction custom field values are not available to Scrips”.
Is adding/fixing this on the radar? I have a temporary fix with an
external process that keeps an eye on the ObjectCustomValues and does
the right thing when there are new, relevant entries (grabs the
appropriate attachment and posts them accordingly), but I’d much rather
use a Scrip.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
After writing a really cool system that allows our RT users to select
from a list of “external source” they want their ticket/reply/comment
posted to (we have a number of “status page” sites), and working up
the
code to make that work… And spending a few hours with a Scrip that
should be working fine, I finally noticed in the wiki that “Note:
as of
3.6.1, per-transaction custom field values are not available to
Scrips”.
Is adding/fixing this on the radar? I have a temporary fix with an
external process that keeps an eye on the ObjectCustomValues and does
the right thing when there are new, relevant entries (grabs the
appropriate attachment and posts them accordingly), but I’d much
rather
use a Scrip.
I believe I posted a patch to the list, but it violated all sorts of
abstraction barriers. I don’t know of a good way to do it
without …doing the wrong thing.
List info: lists.bestpractical.com Mailing Lists
rt-devel
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (Darwin)
iD8DBQFFn/hzEi9d9xCOQEYRAmMzAJ0cr3MApvdCTpkBG/xK2QFiuS+1CACgtfa0
K3U2CRsK7HijXqfp+WA2fRg=
=YAS2
-----END PGP SIGNATURE-----