1 | | Users aren't displayed in the ticket //assign-to// field (TracTickets#Assign-toasDrop-DownList) until they have authenticated with the project (`[ticket] restrict_owner = true`). Some users choose to run a SQL query on the database to insert "known users". To help with this recurring issue we could extend the `session set` command or add a `session promote` command, either of which would effectively execute [browser:/tags/trac-1.0.9/trac/web/session.py@:271#L271 Session.promote_session]. |
| 1 | When `[ticket] restrict_owner = true`, users aren't displayed in the ticket //assign-to// field (TracTickets#Assign-toasDrop-DownList) until they have authenticated with the project. As a workround, some admins choose to run a SQL query on the database to insert "known users". To help with this recurring issue we could extend the `session set` command or add a `session promote` command, either of which would effectively or directly execute [browser:/tags/trac-1.0.9/trac/web/session.py@:271#L271 Session.promote_session]. |
| 2 | |
| 3 | The issue was recently raised again in gmessage:trac-users:vKI_MDGL-Fs/EkAu9fiNCQAJ. |