REPOST: changing custom field value globally

RT Users
1

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

There was one reply to my question but there weren’t any details on how
it was done or if it was actually what I was looking for.

I have a custom field that details customer profile names. Recently, a
profile name has changed and we need the change in RT to be retroactive
to any ticket created under the previous profile. Can I do this within
RT or will I need to run a mass update on the database?

Thanks,
Mathew Snyder
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFDMW0r7cEqtYW7kARAmL4AKCgtdplbbLlgYbM3sRJNrE5GG0NSwCgg9ge
yYGzX9oxV2k0XxMtG8AEzDM=
=O/QM
-----END PGP SIGNATURE-----

2

At Saturday 9/16/2006 11:49 PM, you wrote:

There was one reply to my question but there weren’t any details on how
it was done or if it was actually what I was looking for.

I have a custom field that details customer profile names. Recently, a
profile name has changed and we need the change in RT to be retroactive
to any ticket created under the previous profile. Can I do this within
RT or will I need to run a mass update on the database?

Matthew,

You don’t mention what version of RT you are running - if it’s 3.6,
you can do this from the bulk update page.

If it’s an earlier RT version, I’d strongly recommend not doing a
direct database update, unless you are absolutely sure you know the
RT database schema very well indeed. I find the best way to do this
kind of fix is a perl script that goes against the RT API. A sample
script that might get you started is at
Request Tracker Wiki (rt-adduser).

Steve

3

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

There was one reply to my question but there weren’t any details on
how
it was done or if it was actually what I was looking for.

I have a custom field that details customer profile names.
Recently, a
profile name has changed and we need the change in RT to be
retroactive
to any ticket created under the previous profile. Can I do this
within
RT or will I need to run a mass update on the database?

For the most history-preserving way to do this, I’d probably do a
bulk-update of all tickets with one value to remove the old value and
add the new one.

PGP.sig (186 Bytes)