Dashboard my reminders error after upgrade to RT 4

After upgrading to RT 4 from 3.8.10, I’m seeing several errors in the
dashboard reminders section in the form “Couldn’t find Ticket for
reminder N. Please contact administrator.” Oddly enough, it displays on
all users’ dashboards. This seems to only affect two or three really
old entries as we really don’t use the reminder functionality. It’s
certainly possible that some data was corrupted by my mucking about in
the database or by using RT-Shredder incorrectly before it was merged
into the mainline, but I’m not sure where to start looking.

Thanks,
-Jon

separate tickets, but they don’t really show up unless you go looking
for them. I opened the tickets numbers that the dashboard was
complaining about and resolved them, which seemed to correct the
problem. Any potential issues that this may raise?On 5/20/11 12:54 PM, Jon Tollerton wrote:

After upgrading to RT 4 from 3.8.10, I’m seeing several errors in the
dashboard reminders section in the form “Couldn’t find Ticket for
reminder N. Please contact administrator.” Oddly enough, it displays
on all users’ dashboards. This seems to only affect two or three
really old entries as we really don’t use the reminder functionality.
It’s certainly possible that some data was corrupted by my mucking
about in the database or by using RT-Shredder incorrectly before it
was merged into the mainline, but I’m not sure where to start looking.

Thanks,
-Jon

From my digging, it looks like reminders are actually implemented as separate tickets, but
they don’t really show up unless you go looking for them. I opened the tickets numbers that
the dashboard was complaining about and resolved them, which seemed to correct the problem.
Any potential issues that this may raise?

The usual cause of this is changing your Organization during an
upgrade (or other manual changes to the database), and Reminders can
be global which is why they showed up for everyone. Resolving them
manually is a fine solution.

-kevin> On 5/20/11 12:54 PM, Jon Tollerton wrote:

 After upgrading to RT 4 from 3.8.10, I'm seeing several errors in the dashboard reminders
 section in the form "Couldn't find Ticket for reminder N. Please contact administrator."
 Oddly enough, it displays on all users' dashboards.  This seems to only affect two or three
 really old entries as we really don't use the reminder functionality.  It's certainly
 possible that some data was corrupted by my mucking about in the database or by using
 RT-Shredder incorrectly before it was merged into the mainline, but I'm not sure where to
 start looking.

 Thanks,
 -Jon

Kyle,

I believe that the wiki has some code (scrip) that forces reminders to
"resolved" automatically when the ticket they are attached to is resolved.

Hope this helps.

Kenn
LBNLOn Tue, May 24, 2011 at 6:39 AM, Kevin Falcone falcone@bestpractical.comwrote:

On Mon, May 23, 2011 at 09:05:01PM -0400, Jon Tollerton wrote:

From my digging, it looks like reminders are actually implemented as
separate tickets, but
they don’t really show up unless you go looking for them. I opened
the tickets numbers that
the dashboard was complaining about and resolved them, which seemed to
correct the problem.
Any potential issues that this may raise?

The usual cause of this is changing your Organization during an
upgrade (or other manual changes to the database), and Reminders can
be global which is why they showed up for everyone. Resolving them
manually is a fine solution.

-kevin

On 5/20/11 12:54 PM, Jon Tollerton wrote:

 After upgrading to RT 4 from 3.8.10, I'm seeing several errors in

the dashboard reminders

 section in the form "Couldn't find Ticket for reminder N. Please

contact administrator."

 Oddly enough, it displays on all users' dashboards.  This seems to

only affect two or three

 really old entries as we really don't use the reminder

functionality. It’s certainly

 possible that some data was corrupted by my mucking about in the

database or by using

 RT-Shredder incorrectly before it was merged into the mainline, but

I’m not sure where to

 start looking.

 Thanks,
 -Jon