[prev in list] [next in list] [prev in thread] [next in thread] 

List:       trac
Subject:    [Trac] Flaw in ticket assignee list?
From:       "Emmanuel Blot" <manu.blot () gmail ! com>
Date:       2007-01-30 12:04:08
Message-ID: 8ff37ed30701300404h2f621b7dj8ca1627a037934fe () mail ! gmail ! com
[Download RAW message or body]


I just bumped into an issue which looks like a regression (since the
upgrade to Trac trunk from 0.10.3, using r4665):

The drop-down list used to assign an owner to a ticket is not filled
as (I) expected.
Only a few names among all the users registered on the system appear
in the drop-down list.

The drop-down list content is built from the list of users that own
the `TICKET_MODIFY` permission.

When the `TICKET_MODIFY` permission is only set for the special
"authenticated" user, it seems that the list is not populated - w/ the
exception of the users that own 'parent' permissions, for example the
list of the administrators as TRAC_ADMIN permission leads to grant
TICKET_MODIFY permission.

It seems that perm.get_users_with_permissions('TICKET_MODIFY') ignores
all the authenticated users, but I may be wrong.

Many others have already been authenticated on the system
 select * from session where authenticated=='1';
reports 34 users.

I have not filled in a ticket yet, as I may have missed an important
point, let me know ;-)

Cheers,
Manu

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to trac-users-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---


[prev in list] [next in list] [prev in thread] [next in thread]