Edgewall Software
Modify

Opened 13 years ago

Closed 13 years ago

#4289 closed enhancement (duplicate)

assign-to as drop-down: user needs to have logged in to appear in list

Reported by: mjs@… Owned by: Jonas Borgström
Priority: normal Milestone:
Component: ticket system Version: 0.10.2
Severity: normal Keywords: session
Cc: mjs@… Branch:
Release Notes:
API Changes:

Description

As described on TracTickets#Assign-toasDrop-DownList, for a user to appear in the assign to drop-down list, they need to have logged in first. This easy to forget. (As well as being somewhat annoying: a common use case for me is to create a user and immediately assign them a ticket.)

This should be changed so that users who can login (irrespective of whether they have or not) appear in the list.

Attachments (0)

Change History (4)

comment:1 by Emmanuel Blot, 13 years ago

Keywords: session added; name assign assignto dropdown login removed

I don't see how this could happen easily, as:

  1. the exhaustive list of users that may log in the system may be undefined, depending on the authentication back end
  2. the list may be very long / may grow very fast

However, I think it would be nice if the administrator could provide a list of logins; in other words the drop-down list could be preloaded, but I don't think the preload could be automated.

in reply to:  1 ; comment:2 by mjs@…, 13 years ago

Cc: mjs@… added

Replying to eblot:

I don't see how this could happen easily, as:

  1. the exhaustive list of users that may log in the system may be undefined, depending on the authentication back end
  2. the list may be very long / may grow very fast

With regard to (2), I don't see how a change in the way the list is populated would affect the length of the list, or the speed with which increases in length. I would have thought that in most cases the users who CAN login eventually DO login, so the list length is ultimately the same.

I appreciate that given the way authentication works in Trac, it will be difficult to automatically populate the list. It would be useful if there were some way to pre-populate the list though, as you suggest.

in reply to:  2 comment:3 by Emmanuel Blot, 13 years ago

Replying to mjs@beebo.org:

With regard to (2), I don't see how a change in the way the list is populated would affect the length of the list, or the speed with which increases in length. I would have thought that in most cases the users who CAN login eventually DO login, so the list length is ultimately the same.

If Trac auto-populates the list with all the users available on the system (i.e. users who may log in), this could make the list to go crazy: imagine a company-wide directory, for example.

I think an administrator tool to populate the list if the best-effort solution at this point - with an option to select all the users available on the system, if the admin really wants it.

This feature might be tied to the IUserDirectory interface (#2456)

comment:4 by Christian Boos, 13 years ago

Resolution: duplicate
Status: newclosed

See rather #3580.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain Jonas Borgström.
The resolution will be deleted. Next status will be 'reopened'.
to as closed The owner will be changed from Jonas Borgström to the specified user.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.