ticket,summary,type,release,owner,status,created,modified,_description,_reporter
12233,Comma after a username takes the first drop down user,defect,1.2,Tetsuya Morimoto,new,2015-03-13T20:43:45+01:00,2015-03-13T20:43:45+01:00,"When you are start typing a name, the drop down shows suggestions as expected by the plugin, but as soon as one types comma (,) it is taken as enter and the first user from the drop down is taken by default. 

Eg:
If I have 2 users with names
John (John Lawson) (username : john) and La (La rel joshi)  (username : la)
The drop down will show John and then La rel in that order as soon as I type ""la""
When I press comma, it by default takes John instead of La rel whose username is ""la""

It should take the user who username is ""la"" as soon as I press comma to add a new user. 
",umang.gopani@…
13880,Usernames with spaces regarded as two usernames,defect,1.2,Tetsuya Morimoto,new,2020-09-07T12:06:37+02:00,2020-09-07T12:06:37+02:00,"When using a username including a space the list will create two items with no email address.

example

'Person 1', 'Some Name', 'some@emailaddress.com'

will make a cc list item as 
cc: ""Person, 1""

When selecting in the autocomplete list it looks OK, but in the saved field of the ticket the error occurs.

In regard to this we have tried to remove the flawed user and added a more correct username 'Person1' for the same email address. I.e. we have tried to cleanup the userslist in htpasswd.

The old user is still present in the autocomplete list as well as the new one.

We would possibly want to rebuild the list used for autocompletion. A reset function or similar whithout resetting the whole database.","mats.koponen@…, elisabeth.gardback@…"
8438,Hiding /users from authenticated users,enhancement,0.11,Ryan J Ollos,new,2011-01-25T17:26:06+01:00,2013-03-27T23:34:07+01:00,"Currently /users is exposed to the world.  Therefore, exposing usernames to anyone whether authenticated or not.  This seems like it would be quite the ""security"" issue for privately hosted/managed trac instances.

Perhaps checking the request for an 'authenticated' setting/flag and appropriately redirecting to the default ""forbidden"" page if necessary would be the proper approach?",abrightwell
7362,Link to ldap plugin for name search,enhancement,0.11,Ryan J Ollos,new,2010-07-09T17:34:30+02:00,2010-09-08T10:12:50+02:00,It would be cool if this plugin could make use of the ldap plugin so it could auto complete usernames from a LDAP directory. ,smbrown@…
7605,Plugin is significantly slower than KeywordSuggestPlugin,defect,0.11,Ryan J Ollos,new,2010-09-01T02:05:20+02:00,2019-05-09T19:05:15+02:00,"Using KeywordSuggestPlugin as a metric, it seems like we should be able to make this plugin more responsive.

{{{
#!email
-----Original Message-----
From: Steffen Hoffmann
Sent: Tuesday, August 31, 2010 11:00
To: Ryan Ollos
Subject: Re: Trac developer discussion - was: Re: Re2: regarding WikiTicketCalendarMacro display width control

> KeywordSuggest is very fast to bring up the list of suggestions from
> a list of several hundred tags. AutocompleteUsers on the other hand
> is not very responsive, and takes 1-3 seconds to make suggestions
> from a list of 15 users. If you are seeing this same behavior, I'll
> start looking at the code and see if we can optimize it somehow. If
> not, perhaps it has something more to do with my Trac installation.

Right, see this as well. Even worse, the AutocompleteUsers sometimes
stopped work at all. Not done too much research on the matter, but I
remember having seen all currently available keywords packed into a list
plus a JS function in the header of HTML pages. While the lookup is done
in the local browser instance, AutocompleteUsers will certainly do
different, so bound to be slower and seemingly more complicated.
}}}",Ryan J Ollos
10155,Autocomplete fields on the custom query page,enhancement,0.11,Ryan J Ollos,reopened,2012-07-17T07:52:43+02:00,2013-03-21T21:10:49+01:00,"Autocomplete the ''cc'', ''owner'' and ''reporter'' fields on the custom query page, as suggested by falkb.",Ryan J Ollos
4442,"Discussion of ""Special Keyword"" for AutoCompleteUsersPlugin",enhancement,0.11,Ryan J Ollos,new,2009-01-13T11:27:09+01:00,2012-07-16T06:18:53+02:00,"Good day!

I've been using the AutocompleteUsersPlugin for quite some time now and it's extremely useful.  I have the desire for a new feature/enhancement, so I figured I'd mention it to you to see what you thought.

Goal:  Ability to CC ""ALL USERS"" of the trac system.
Use Case: Say we have a new ticket of type ""Notice"".  Typically, one might want to send the notice to all of the trac users that use the system, or, perhaps to particular groups (as defined in the permissions system).

Do you think this is possible?  Some potential keywords I was thinking off:
|| Keyword || Purpose || Comments ||
|| all-users || To CC all currently registered users. || Get the current list of registered trac users, and the AJAX would auto-fill the keyword ""all-users-now"" to the currently list of registered users (comma separated usernames) into the CC box. ||
|| @group || To CC all users of the permission group ""group"". || This would also auto-fill any keyword preceding with the ""@"" symbol, with the group members as defined on the ''permissions'' Admin page ||",Matt Callaghan
12092,"Autocomplete users in the Timeline ""done by"" filter",enhancement,,Tetsuya Morimoto,new,2014-12-05T00:53:04+01:00,2020-05-01T06:51:13+02:00,"Mentioned in gmessage:trac-users:183g75yH65w/YgJ-q8AREpwJ, it would be nice to autocomplete usernames in the timeline ""done by"" filter.",Ryan J Ollos
12984,Completion list is broken when vertical bar is used in name or email of the user,defect,,Tetsuya Morimoto,new,2016-12-08T04:34:09+01:00,2020-05-01T06:51:13+02:00,[[Image(broken-completion.png)]],Jun Omae