We’ve taken the code in “MyTickets” and modified it to form a new module.
With the new code, instead of limiting the list to the current user, it is
limited to “Nobody”, thus allowing everyone to easily see which tickets have
got the highest priority but no owners.
That is all working fine.
However, we’ve now added a second queue. Not a problem, you might think. The
problem comes when some of the privileged users have rights on one queue but
not the other.
What seems to be happening is that the code is taking the list of tickets,
limiting them by owner & status, then taking the first N rows and then
So what is wrong with that?
Well, if the current user doesn’t have privilege on both queues, and the
first N tickets (in priority order) all belong to the other queue, the above
code displays no tickets at all.
What I want/need/would like to see happen is for the list of tickets to be
filtered by what the user has rights over first of all, before anything else
I had sort of expected that, given that “new RT::Tickets” takes the current
user session has a parameter.
Philip Colmer, MBCS CEng CCSE Tel: 01223 271223
I.T. Manager Fax: 01223 215513
ProQuest Information & Learning
The Quorum, Barnwell Road, Cambridge, CB5 8SW