John Arends wrote:
I poked around in the database a bit, especially in the Tickets table, but couldn't find anything related to reminders. Do you know where I should be looking?

Michael Finn wrote:
When I've come across an "undeletable" reminder, it has always been the
case that the associated ticket was moved to a different queue *after*
the reminder was created.  Thus the reminder (which is stored in the
same "Tickets" table in the DB) now has a different queue number than
its associated ticket.  Changing the queue on the reminder (using SQL)
so that it matches the queue on the ticket should clear up your problem,
if this is what has happened to you as well.

Cheers,
Mike

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of John
Arends
Sent: Tuesday, March 20, 2007 11:16 AM
To: rt-users@lists.bestpractical.com
Subject: [rt-users] Phantom Reminder

I have a reminder that is owned by 'Nobody' that shows up on the front page when I am logged into the system as root. Clicking on the reminder link takes me into the ticket under which the reminder was created.

However, when I am in that ticket, no reminders are shown. The ticket has been resolved, but I tried setting the status back to open just for
fun.

When logged in as my normal user, I can't see the reminder, but when I log in with 2 different accounts that are superusers, I can see the reminder on RT at a glance.

How do I make this thing go away?
I suspect the problem is the Queue bit of the SQL query in lib/RT/Reminders.pm in Collection (line 88 in 3.6.HEAD). I'm running without it here and things are better. Still problems closing a reminder if you don't have proper perms on
the original queue.

Jeff Voskamp
_______________________________________________
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

Reply via email to