RT 3.8.2 question

To all,

We are planning to move up to 3.8.2 soon (a month?). One of the tings 

my users do not like is that there are many CF’s that are sowing up in
their “Modify Ticket” screen that some use, some don’t ,but needs to be
available for all. They want to be able to move the one’s they do NOT
use (individually) out of the way (to the far right and to the bottom).
Is this something that is offered as a feature in 3.8.2 or do we need to
modify code? Thanks.

Kenn
LBNL

Slightly confusing instructions (and different from 3.8.0) on upgrading a
mysql database.

First, the instructions say to run /opt/rt3/sbin/rt-setup-database telling
the script the current version you are running. Then they say to stop the
upgrade at 3.8.0 and then run:

etc/upgrade/upgrade-mysql-schema.pl, blah, blah, blah.

Then run /opt/rt3/sbin/rt-setup-database to apply the rest of the upgrades.

So, in the setup-database script, do you tell it to stop at 3.8.0, or
3.7.87? Meaning, if I choose 3.8.0, does the script stop after installing
the 3.7.87 schema changes, or does it also include the 3.8.0 schema
updates? Perhaps it doesn’t matter.

James Moseley

Slightly confusing instructions (and different from 3.8.0) on upgrading a
mysql database.

First, the instructions say to run /opt/rt3/sbin/rt-setup-database telling
the script the current version you are running. Then they say to stop the
upgrade at 3.8.0 and then run:

etc/upgrade/upgrade-mysql-schema.pl, blah, blah, blah.

Then run /opt/rt3/sbin/rt-setup-database to apply the rest of the upgrades.

So, in the setup-database script, do you tell it to stop at 3.8.0, or
3.7.87? Meaning, if I choose 3.8.0, does the script stop after installing
the 3.7.87 schema changes, or does it also include the 3.8.0 schema
updates? Perhaps it doesn’t matter.

I don’t believe it actually matters, but the intent was to stop before
the 3.8.0 updates, run the script and continue. Documentation patches
would be lovely.

So, in the setup-database script, do you tell it to stop at 3.8.0, or
3.7.87? Meaning, if I choose 3.8.0, does the script stop after
installing

the 3.7.87 schema changes, or does it also include the 3.8.0 schema
updates? Perhaps it doesn’t matter.

I don’t believe it actually matters, but the intent was to stop before
the 3.8.0 updates, run the script and continue. Documentation patches
would be lovely.

How’s this for a start:

— UPGRADING.mysql 2009-01-06 19:15:20.000000000 -0600
+++ UPGRADING.mysql.patched 2009-01-09 08:34:51.000000000 -0600
@@ -19,7 +19,7 @@

  1. Follow instructions in the README file to step 7.

-3) Apply changes described in step 7, but only up to version 3.8.0.
+3) Apply changes described in step 7, but only up to and not including
version 3.8.0.

  1. Apply the MySQL 4.0->4.1 schema changes. Included in RT is the script
    etc/upgrade/upgrade-mysql-schema.pl that generates SQL queries to upgrade
    the database’s schema. Run it:
    @@ -40,8 +40,8 @@
    your database from the backup you made at step 1) and send a report to the
    rt-users@lists.bestpractical.com mailing list.

-7) Continue from step 7 in the README and apply other upgrade scripts and
follow
-other steps.
+7) Continue from step 7 in the README and apply other mysql upgrade
scripts and follow
+remaining steps.

  1. Test everything. The most important parts you have to test:
  • binary attachments, like docs, PDFs, and images

James

the 3.8.0 updates, run the script and continue. Documentation patches
would be lovely.

How’s this for a start:

Thanks. Applied with some tweaks

To all,
We are planning to move up to 3.8.2 soon (a month?). One of the tings
my users do not like is that there are many CF’s that are sowing up in
their “Modify Ticket” screen that some use, some don’t ,but needs to be
available for all. They want to be able to move the one’s they do NOT
use (individually) out of the way (to the far right and to the bottom).
Is this something that is offered as a feature in 3.8.2 or do we need to
modify code? Thanks.
I’ve never seen any such thing, and would use GreaseMonkey or another
client solution rather than monkeying with the the codebase.

Cambridge Energy Alliance: Save money. Save the planet.