Strange behavious after upgrading from RT2 -> RT3.6.7

RT Users
1

I just upgraded our old RT 2 instance to the latest and greatest (3.6.7)
and most things seem to work just fine.

However, I just noticed a strange thing. If I open a ticket and
hit “Reply” then things look a bit strange below the section:

This message will be sent to...

Ie, like this:

This message will be sent to…
(Check boxes to disable notifications to the listed recipients)

On Correspond Notify AdminCcs with template Admin Correspondence

On Correspond Notify Requestors and Ccs with template Correspondence

On Correspond Notify Other Recipients with template Correspondence

Imported from RT 2.0
On Transaction Notify Owner with template Transaction

Imported from RT 2.0
On Transaction Notify AdminCcs with template Transaction

Messages about this ticket will not be sent to…
(Check boxes to enable notifications to the listed recipients)

Now, I’m new to RT3, so perhaps this is the way it’s supposed to be,
but to my eyes this looks strange.

(See the attached JPG image of an actual screendump)

Is this how things should look or did something go wrong
in our upgrade?

We used the rt2-to-rt3-1.23 tool to dump the database,
then installed it into an RT 3.2.3 instance, and then ran
the upgrade scripts in RT 3.6.7’s etc/upgrade directory
per the documentation (we ran the “3.3.0”, “3.3.11” and “3.5.1”
directories).

Should we have also ran the 3.1.0, 3.1.15 and 3.1.17
directories too? (I skipped those since we used RT 3.2.3
when importing the database).

  • Peter

signature.asc (185 Bytes)

2

I just upgraded our old RT 2 instance to the latest and greatest
(3.6.7)
and most things seem to work just fine.

However, I just noticed a strange thing. If I open a ticket and
hit “Reply” then things look a bit strange below the section:

This message will be sent to…

Ie, like this:

This message will be sent to…
(Check boxes to disable notifications to the listed recipients)

On Correspond Notify AdminCcs with template Admin Correspondence

On Correspond Notify Requestors and Ccs with template Correspondence

On Correspond Notify Other Recipients with template Correspondence

Imported from RT 2.0
On Transaction Notify Owner with template Transaction

Imported from RT 2.0
On Transaction Notify AdminCcs with template Transaction

Messages about this ticket will not be sent to…
(Check boxes to enable notifications to the listed recipients)

Now, I’m new to RT3, so perhaps this is the way it’s supposed to be,
but to my eyes this looks strange.

(See the attached JPG image of an actual screendump)

Is this how things should look or did something go wrong
in our upgrade?

We used the rt2-to-rt3-1.23 tool to dump the database,
then installed it into an RT 3.2.3 instance, and then ran
the upgrade scripts in RT 3.6.7’s etc/upgrade directory
per the documentation (we ran the “3.3.0”, “3.3.11” and “3.5.1”
directories).

There are newer versions of that tool, have a look at
http://download.bestpractical.com/pub/rt/devel/rt2-to-rt3.README
These would have allowed you to go to 3.6.7 directly

You can probably remove all the ‘Imported from RT 2.0’ scrips unless
you had customizations you needed to port over.

As for why RT doesn’t want to mail anyone, you didn’t provide
enough information to know why that was.

-kevin

3

Peter,

It really isn't as bad as it may seem. All RT is telling you on that

display page is the scrips that are going to be triggered by your
transaction (your “Reply”). Let me explain. When you clicked “Reply” you
told RT that you intend to “Correspond”. RT is letting you know what it
is planning to do once you click “Update Ticket”. Based on your screen
shot, RT will:

  1. Send an Email notification (using the “Admin Correspondence”
    template) to those users listed as AdminCc “Watchers” for the queue in
    which the ticker resides.

  2. Send an Email notification (using the “Correspondence” template) to
    those users listed as Cc “Watchers” for the queue in which the ticker
    resides as well as the “Requestor” for that particular ticket.

  3. Send an Email notification (using the “Correspondence” template) to
    those users listed as additional “Cc” recipients for that particular ticket.

    These are the Global Notification scrips that are currently enabled in
    your RT 3.6.7 session.
    Additionally, RT is ALSO planning on executing two other notification
    scrips that were part of your older version and were transferred over to
    this current version. All told, RT is telling you that it has 5 enabled
    Notification scrips that it intends to execute.
    What you need to do is look at these scrips and decide if you want them
    to execute at all; at the global level, or just for a specific queue.
    Then either modify when/where they will execute, if at all. Hope this helps.

Kenn
LBNLOn 7/4/2008 3:58 AM, Peter Eriksson wrote:

I just upgraded our old RT 2 instance to the latest and greatest (3.6.7)
and most things seem to work just fine.

However, I just noticed a strange thing. If I open a ticket and
hit “Reply” then things look a bit strange below the section:

This message will be sent to…

Ie, like this:

This message will be sent to…
(Check boxes to disable notifications to the listed recipients)

On Correspond Notify AdminCcs with template Admin Correspondence

On Correspond Notify Requestors and Ccs with template Correspondence

On Correspond Notify Other Recipients with template Correspondence

Imported from RT 2.0
On Transaction Notify Owner with template Transaction

Imported from RT 2.0
On Transaction Notify AdminCcs with template Transaction

Messages about this ticket will not be sent to…
(Check boxes to enable notifications to the listed recipients)

Now, I’m new to RT3, so perhaps this is the way it’s supposed to be,
but to my eyes this looks strange.

(See the attached JPG image of an actual screendump)

Is this how things should look or did something go wrong
in our upgrade?

We used the rt2-to-rt3-1.23 tool to dump the database,
then installed it into an RT 3.2.3 instance, and then ran
the upgrade scripts in RT 3.6.7’s etc/upgrade directory
per the documentation (we ran the “3.3.0”, “3.3.11” and “3.5.1”
directories).

Should we have also ran the 3.1.0, 3.1.15 and 3.1.17
directories too? (I skipped those since we used RT 3.2.3
when importing the database).

  • Peter

The rt-users Archives

Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.com

Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com