#12838: Rights caching in "new ticket in" queue display

# Thu Dec 11 15:24:13 2008 Shawn Moore - Status changed from 'open' to 'resolved'

# Fri Nov 28 13:28:32 2008 The RT System itself - Status changed from 'new' to 'open'

# Fri Nov 28 13:28:31 2008 The RT System itself - Outgoing email recorded [Show]

# Fri Nov 28 13:28:30 2008 The RT System itself - Outgoing email recorded [Show]

# Fri Nov 28 13:28:29 2008 Jesse Vincent - Correspondence added [Reply] [Comment]

CC:	undisclosed-recipients: ;
Subject:	Re: [fsck.com #12838] AutoReply: Rights caching in "new ticket in" queue display
Date:	Fri, 28 Nov 2008 13:28:23 -0500
To:	"dominic.hargreaves@oucs.ox.ac.uk via RT" <rt-bugs@bestpractical.com>
From:	Jesse Vincent <jesse@bestpractical.com>

Download (untitled) / with headers
text/plain 1.1k

"By design"

Adding new queues is a very infrequent operation. The list of "what
queues can I see" is a VERY frequently used list. And it's relatively
expensive to calculate.

There's an explicit cache for the queue list that lasts for your
session.

On Mon 24.Nov'08 at 7:43:03 -0500, dominic.hargreaves@oucs.ox.ac.uk via RT wrote:

>
> <URL: http://rt3.fsck.com//Ticket/Display.html?id=12838 >
>
> On Mon, Nov 24, 2008 at 07:34:55AM -0500, Bugs in RT 3.x via RT wrote:

> > Using RT 3.8.1.
> >
> > If I log into RT with a user who has permission to see some, but not all
> > queues, then the queues I have the rights to see are correctly listed in the
> > 'new ticket in' dropdown.
> >
> > If I am then given the rights to see some more queues, although the rights have
> > clearly taken effect (the 'RT at a glance' summaries now show tickets I
> > couldn't see before), the queues do not appear in the 'new ticket in' dropdown
> > until I delete my cookies for the RT server (or close my browser).

>
> P.S. Reproduced with postgres and sqlite.
>
> --
> Dominic Hargreaves, Systems Development and Support Team
> Computing Services, University of Oxford
>

--

Download (untitled)
application/pgp-signature 194b

Message body not shown because it is not plain text.

# Mon Nov 24 07:43:03 2008 The RT System itself - Outgoing email recorded [Show]

# Mon Nov 24 07:43:02 2008 dominic.hargreaves@oucs.ox.ac.uk - Correspondence added [Reply] [Comment]

Subject:	Re: [fsck.com #12838] AutoReply: Rights caching in "new ticket in" queue display
Date:	Mon, 24 Nov 2008 12:40:48 +0000
To:	"Bugs in RT 3.x via RT" <rt-bugs@bestpractical.com>
From:	Dominic Hargreaves <dominic.hargreaves@oucs.ox.ac.uk>

Download (untitled) / with headers
text/plain 729b

On Mon, Nov 24, 2008 at 07:34:55AM -0500, Bugs in RT 3.x via RT wrote:

> Using RT 3.8.1.
>
> If I log into RT with a user who has permission to see some, but not all
> queues, then the queues I have the rights to see are correctly listed in the
> 'new ticket in' dropdown.
>
> If I am then given the rights to see some more queues, although the rights have
> clearly taken effect (the 'RT at a glance' summaries now show tickets I
> couldn't see before), the queues do not appear in the 'new ticket in' dropdown
> until I delete my cookies for the RT server (or close my browser).

P.S. Reproduced with postgres and sqlite.

--
Dominic Hargreaves, Systems Development and Support Team
Computing Services, University of Oxford

# Mon Nov 24 07:34:57 2008 The RT System itself - Outgoing email recorded [Show]

# Mon Nov 24 07:34:56 2008 The RT System itself - Outgoing email recorded [Show]

# Mon Nov 24 07:34:54 2008 Guest - Ticket created [Reply] [Comment]

Subject:

Rights caching in "new ticket in" queue display

Download (untitled) / with headers
text/html 538b

Using RT 3.8.1.

If I log into RT with a user who has permission to see some, but not all queues, then the queues I have the rights to see are correctly listed in the 'new ticket in' dropdown.

If I am then given the rights to see some more queues, although the rights have clearly taken effect (the 'RT at a glance' summaries now show tickets I couldn't see before), the queues do not appear in the 'new ticket in' dropdown until I delete my cookies for the RT server (or close my browser).