Can't remove user from Assign to list, even if all permissions for that user are removed

[lewis+trac@…]

If Trac is configured with restrict_owner = true and you remove all permissions for given authenticated user, that user will still show up in the Assigned to select.

Seems to me that a user with no permissions should not show up as a potential assigned to target.

[anonymous]

I'm a very new user .. and created new authenticated users - but how do i set their permissions/password etc?

[Emmanuel Blot]

Replying to anonymous:

I'm a very new user .. and created new authenticated users - but how do i set their permissions/password etc?

Please read the NewTicket page: support questions are to be posted to the MailingList.

[Remy Blank]

This is by design. The owner with no permissions is only visible on tickets already assigned to him. If this wasn't the case, it would not be possible to edit such a ticket without changing the owner.

If you reassign such a ticket to another user, the user with no permissions will disappear from the list for that ticket.

[anonymous]

@rblank: I call foul on closing this - based on the ticket summary/description, your resolution comment is a bit nonsensical.

So for anyone else who comes across the actual (very real) problem described in the ticket, the actual answer is here: ​gdiscussion:trac-users:Qi_NXpDYxQ8.

[anonymous]

Replying to rblank:

This is by design. The owner with no permissions is only visible on tickets already assigned to him. If this wasn't the case, it would not be possible to edit such a ticket without changing the owner.

If you reassign such a ticket to another user, the user with no permissions will disappear from the list for that ticket.

I agree that this ticket should not be closed

If you had old tickets with developers not working here anymore, we still want those tickets to show their names.

However going through a list of 100 names to assign the ticket to one of a possible 5 - 10 persons is ridiculous. Old users should still be allowed to be seen as the person who attended to a ticket 10 years ago, but it doesn't mean that he should be available to be assigned a new ticket.

[Ryan J Ollos]

Replying to anonymous:

So for anyone else who comes across the actual (very real) problem described in the ticket, the actual answer is here: ​gdiscussion:trac-users:Qi_NXpDYxQ8.

It is not necessary to delete the session in order to remove the user from the assign-to dropdown list.

[Ryan J Ollos]

Replying to anonymous:

However going through a list of 100 names to assign the ticket to one of a possible 5 - 10 persons is ridiculous. Old users should still be allowed to be seen as the person who attended to a ticket 10 years ago, but it doesn't mean that he should be available to be assigned a new ticket.

I see the same behavior described in comment:4 on 1.0-stable, and I agree with rblank's assertion that the existing behavior is correct. I cannot reproduce the behavior described in comment:6.

The most likely explanation of the behavior described in comment:description, comment:5 and comment:6 is that TICKET_MODIFY is granted to authenticated users. Please use TracAdmin to confirm that the user does not possess TICKET_MODIFY:

$trac-admin ../proj-1.0/ permission list user2

User   Action             
--------------------------
user2  BROWSER_VIEW       
user2  CHANGESET_VIEW     
user2  FILE_VIEW          
user2  INVALID_PERM       
user2  LOG_VIEW           
user2  MILESTONE_VIEW     
user2  REPORT_SQL_VIEW    
user2  REPORT_VIEW        
user2  ROADMAP_VIEW       
user2  SEARCH_VIEW        
user2  TICKET_BATCH_MODIFY
user2  TICKET_CREATE      
user2  TICKET_VIEW        
user2  TIMELINE_VIEW      
user2  WIKI_CREATE        
user2  WIKI_MODIFY        
user2  WIKI_VIEW          


Available actions:
 BROWSER_VIEW, CHANGESET_VIEW, CONFIG_VIEW, EMAIL_VIEW, FILE_VIEW,
 LOG_VIEW, MILESTONE_ADMIN, MILESTONE_CREATE, MILESTONE_DELETE,
 MILESTONE_MODIFY, MILESTONE_VIEW, PERMISSION_ADMIN, PERMISSION_GRANT,
 PERMISSION_REVOKE, REPORT_ADMIN, REPORT_CREATE, REPORT_DELETE,
 REPORT_MODIFY, REPORT_SQL_VIEW, REPORT_VIEW, ROADMAP_ADMIN, ROADMAP_VIEW,
 SEARCH_VIEW, TICKET_ADMIN, TICKET_APPEND, TICKET_BATCH_MODIFY,
 TICKET_CHGPROP, TICKET_CREATE, TICKET_EDIT_CC, TICKET_EDIT_COMMENT,
 TICKET_EDIT_DESCRIPTION, TICKET_MODIFY, TICKET_VIEW, TIMELINE_VIEW,
 TRAC_ADMIN, VERSIONCONTROL_ADMIN, WIKI_ADMIN, WIKI_CREATE, WIKI_DELETE,
 WIKI_MODIFY, WIKI_RENAME, WIKI_VIEW

Users lacking TICKET_MODIFY will not be included in the assign-to select box.