'Assign to' as popup list

[anonymous]

It would be nice to add developers for 'Assign to' with trac-admin and have them show up in a popup list like the other ticket properties. This would eliminate the possibility of mis-spelled names.

[anonymous]

…and generally make it easier to set the field.

[daniel]

Hmm, maybe it'd be useful to have a popup with 'registered' users and populate the field entirely with javascript… that'd be more flexible than having to duplicate the interface.

[daniel]

Having the Session architecture, we could potentially use that data. It might be a too extensive list though.

[Christopher Lenz]

#573 has been marked as duplicate of this ticket. See that ticket for further comments.

[ivanoe@…]

patch: solution to the ticket using both apache password or trac 'permission' table's 'username'

[ivanoe@…]

The attachment ​trac.ticket.222.diff solves the issue in following ways:

• If the Environment variable TRAC_PWDFILE is defined in the httpd.conf Apache configuration, the list of users is taken from this passwordfile:

  ...
  <Location "/trac">
     SetEnv TRAC_ENV /path/to/trac/project_trac.db
     SetEnv TRAC_PWDFILE "path/to/subversionpassword"
  </Location>
  ...
  

The value of TRAC_PWDFILE should be the same as the one configured for AuthUserFile in section:

...
<Location "/trac/login">
  ...
  AuthUserFile "path/to/subversionpassword"
  ...
</Location>
...

• Otherwise, the list of users is taken from the 'permission' table in trac.db. Only the end-users are included. The groups as explained in TracPermissions are not returned as is not 'anonymous' user.
• Empty string is also added to the list.

Please note: I tested only on Windows.

It could be cool if included into 0.8, but I am afraid that might be a bit too late for that…

[ivanoe]

dummpy comment as it seems that the last change did not appear in the timeline.

[ivanoe]

please ignore the changes to header.cs in the patch - they are related to the other change

[Jonas Borgström]

This is a good idea but unfortunately we don't have way to get a complete list of available users without adding auth-specific code to Trac. I don't even think that's possible with some auth modules.

This will probably have to wait until Trac 2.0 where we will have real user support.

[Christopher Lenz]

#876 has been marked as a duplicate of this bug. That ticket also has a patch.

[Christopher Lenz]

#1028 has been marked as duplicate of this one. That ticket also has a patch.

[Christopher Lenz]

Slightly reworked pkou's patch from ticket #1028

[pkou <pkou at ua.fm>]

The updated patch looks OK for me. Thank you for the feedback.

[Josh Burley <jburley@…>]

This is working great for me, now. Awesome! This feature has basically gotten Trac accepted here :D (am consulting for a department within a Fortune 100 company).

[Christopher Lenz]

This has been implemented in [1342]. The part of the patch related to sending ticket notifications to ticket owners will come later… Thanks pkou!

[anonymous]

The always_notify_owner option included in the patch will be tracked using #866.

[dserodio@…]

Where is the list of users is taken from after all? In [1342], I can see a get_known_users method which queries

SELECT DISTINCT s.username, n.var_value, e.var_value 
FROM session AS s 
LEFT JOIN session AS n ON (n.sid IS NULL 
 AND n.username=s.username AND n.var_name = 'name') 
LEFT JOIN session AS e ON (e.sid IS NULL 
 AND e.username=s.username AND e.var_name = 'email') 
WHERE s.sid IS NULL ORDER BY s.username

But if I run this query on the SQLite prompt, I get:

SQL error: no such column: s.username

[anonymous]

Adding dummy comment because the previous one didn't make it to the Timeline

[Christopher Lenz]

Look at the current version of get_known_users() in trac.env​.

Anyway, to answer your question, the set of user names is retrieved from the session table, which should contain all the users that ever logged in.

[dserodio@…]

Thanks, now I achieved what I wanted: to "pre-fill" the set of user names with users that have never logged in.

See attached trac-users.py​ utility script that generates the INSERT statements for users contained in a htdigest or htpasswd files.

[dserodio@…]

Generates INSERT statements for Trac users in a htdigest file, so they show up in the "owner" drop-down.

[dserodio@…]

Oops, authenticated should be 1, not 0

[bootsch]

Did someone create a patch for use with version 0.9.x? The provided patches work on 0.8.x correct?

I really like the feature ;-) but had to move to 0.9 ;-(

[anonymous]

Did you not see that this is now part of the core Trac? It was done in [1342] and is documented in TracIni. Look for restrict_owner.

[anonymous]

Oops, I missed that indeed, thank you for pointing that out

[mmcneil@…]

How can I delete the username of an old user from this assign-to drop-down list? Is there any way I can edit or pre-populate this list?

[Emmanuel Blot]

There is no current way to edit this list, but tweaking the DB (using SQL commands).
Please ask further questions about this topic on the ML.

[Emmanuel Blot]

See #1347 for a WebAdmin-based solution.

[landpro]

Hello! Can I use this patch with 10.4 version? If yes then how?

Thank you in advance.

[anonymous]

How do you actually turn this on ?

[mrelbe <mikael@…>]

Replying to anonymous:

How do you actually turn this on ?

The answer is stated in comment:26 above:

…and is documented in TracIni. Look for restrict_owner.