Re: [rt-users] changing Organization
On 02/12/13 16:56, Alex Vandiver wrote: On Fri, 2013-11-29 at 13:11 +, Jenny Martin wrote: I would like to change our Organization name to avoid confusion with another RT instance? Does anyone have a script to fixup the RT database so that I can change the Organization name without breaking the RT ticket links? RT 4.2's sbin/rt-validator has a --links-only which, in conjunction with --resolve, will fix links after an Organization change. - Alex Many thanks. We are still on 4.0.17, so perhaps I will wait to change Organization until we upgrade to 4.2.
Re: [rt-users] changing Organization
On Fri, 2013-11-29 at 13:11 +, Jenny Martin wrote: I would like to change our Organization name to avoid confusion with another RT instance? Does anyone have a script to fixup the RT database so that I can change the Organization name without breaking the RT ticket links? RT 4.2's sbin/rt-validator has a --links-only which, in conjunction with --resolve, will fix links after an Organization change. - Alex
Re: [rt-users] changing $Organization
On 01/31/2013 04:01 PM, Christoph Badura wrote:
Our setting of $Organization has included a blank because the version of
RT I installed originally didn't yet complain about blanks in $Organization.
We're getting tired :-) of the related warnings on upgrades and I'm trying
to fix the references in the database this week.
I've found and fixed references in the Links and Transactions tables.
Is any other table to be fixed? Is there maybe a canonical list of tables
and columns to fix?
The 4.2 version of sbin/rt-validator catches and fixes $Organization
changes. You could grab that and use it on your 4.0 database with the
--links-only option. However, if you're sure you've already fixed all
occurrences in Links and Transactions, then it wouldn't find anything as
this is where it looks:
my @URI_USES = (
{ model = 'Transaction', column = 'OldValue', Additional = {
Type = 'DeleteLink' } },
{ model = 'Transaction', column = 'NewValue', Additional = {
Type = 'AddLink' } },
{ model = 'Link', column = 'Target' },
{ model = 'Link', column = 'Base' },
);
Re: [rt-users] Changing $Organization in RT_Config
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 4 Apr 2007 at 07:41 (+0900), Jesse Vincent wrote: What kind of things might break if I change the value of $Organization while continuing to use the same database as before (after upgrading the schema, of course)? You'll break all the links between tickets. Jesse, OK, thanks. I guess I can live with the existing value of $Organization. Mike _ Mike FriedmanInformation Services Technology [EMAIL PROTECTED] 2484 Shattuck Avenue 1-510-642-1410 University of California at Berkeley http://socrates.berkeley.edu/~mikef http://ist.berkeley.edu _ -BEGIN PGP SIGNATURE- Version: PGP 6.5.8 iQA/AwUBRhQdPa0bf1iNr4mCEQIXIgCeIChkIcZQAyW9k5nHquDLW9sNm5QAn2eZ myG7sIVnINWKJAFhzblyMemN =lAQe -END PGP SIGNATURE- ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
Re: [rt-users] Changing $Organization in RT_Config
On Apr 4, 2007, at 5:10 AM, Mike Friedman wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I've consulted the list archives about this, but have not seen a definitive answer to my specific question, which is: What are the practical consequences of changing the value of $Organization in the RT config? This is separate from the question of $rtname, which I know about. The comment in RT_Config says that $Organization is used by the linking interface to guarantee that ticket URIs are unique and easy to construct. Which URIs make use of $Organization? I'm about to upgrade from RT 3.4.5 to 3.6.3. I've done a clean install in a new environment and plan to move over my existing database that's been running with 3.4.5. However, for various reasons (the domain name isn't really appropriate any more, for one thing), if possible I'd like the value of $Organization to better reflect the new auspices under which this RT will be running. What kind of things might break if I change the value of $Organization while continuing to use the same database as before (after upgrading the schema, of course)? You'll break all the links between tickets. Best, Jesse Thanks. Mike __ ___ Mike FriedmanInformation Services Technology [EMAIL PROTECTED] 2484 Shattuck Avenue 1-510-642-1410 University of California at Berkeley http://socrates.berkeley.edu/~mikef http://ist.berkeley.edu __ ___ -BEGIN PGP SIGNATURE- Version: PGP 6.5.8 iQA/AwUBRhK0060bf1iNr4mCEQLLHgCghSZjoul0gfH90mRGKEA+Gl762boAnA1b gvPZ0Do4V+oUfwHlQ0WjHsIo =tY4U -END PGP SIGNATURE- ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com PGP.sig Description: This is a digitally signed message part ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
