Edgewall Software
Modify

Opened 8 years ago

Last modified 4 years ago

#3737 new enhancement

login-id, trac-nick

Reported by: ThurnerRupert <rupert.thurner@…> Owned by: jonas
Priority: normal Milestone: next-major-releases
Component: general Version: devel
Severity: normal Keywords: username user
Cc: d.grellscheid@…, jeremyk@…, ryano@…, itamarost@…
Release Notes:
API Changes:

Description

as also noted in #3667 there are cases where the username may change. also login mechanisms coming via basic auth may provide some userid which is not easy to remember. therefor it would be great to have more fields for a user, i.e. a username, userid, a nick, and maybe the nick is displayed.

Attachments (0)

Change History (22)

comment:1 Changed 8 years ago by ThurnerRupert

  • Summary changed from userid, username to login-id, trac-nick

the goal of this ticket

provide easy to rembember usernames/nicks/trac-user-id (the "sid" in the session table) for everything, be it query, assigning tickets, rights, setting cc.

this means that the sid needs to be decoupled from the login-id, which can be a quit unrememberable beast.

implementation possibility?

would it be possible to store the login-id in the session_attribute table and offer a button/function to change the nick (stored as "sid" in the session table?

or add a "login-id" to the session table to allow easier setting a unique key on it?

comment:2 follow-up: Changed 8 years ago by ThurnerRupert

#4210 marked as duplicate.

comment:3 in reply to: ↑ 2 ; follow-up: Changed 8 years ago by anonymous

Replying to ThurnerRupert:

#4210 marked as duplicate.

Any ideas as far as (a) feasibility of this enhancement and (b) milestone to attach it to?

comment:4 Changed 8 years ago by sid

#3032 was marked as duplicate of this ticket.

comment:5 in reply to: ↑ 3 ; follow-up: Changed 8 years ago by anonymous

Replying to anonymous:

Replying to ThurnerRupert:

#4210 marked as duplicate.

Any ideas as far as (a) feasibility of this enhancement and (b) milestone to attach it to?

  1. feasibility: as it just touches the login code, the (coding) impact should be small.
  2. milestone: jonas/cboos/… are in a better position to answer that question.

comment:6 in reply to: ↑ 5 Changed 8 years ago by cboos

  • Keywords username added
  • Milestone set to 0.12

Replying to anonymous:

  1. milestone: jonas/cboos/… are in a better position to answer that question.

I'd say a patch for 0.11 could be considered, otherwise it seems more in line with what we already scheduled for 0.12 (which I'm assigning this ticket to, so that it doesn't get lost).

comment:7 Changed 8 years ago by cboos

Another request for this in #4559 (for showing the full name in the Assign to drop down list, so it's exactly like #4210).

comment:8 Changed 8 years ago by ThurnerRupert

#4553 reqests to display the full username instead of the subversion login id and also trac user id coming from ldap. also suggests to use tooltips to display the user name.

mark as dup hoping that the problem is cryptic user names which would be solved by nick-names.

comment:9 Changed 7 years ago by eblot

#4713 has been marked as a duplicate

comment:10 Changed 7 years ago by anonymous

I would be much more into the 'name' field, which is already being gathered, to be displayed on views instead of the login id. This could be a config change in the trac.ini to hit some display logic.

comment:11 follow-up: Changed 7 years ago by ThurnerRupert

it is not just a display issue. if you assign tickets, if you query tickets, if you search for tickets you've to know this cryptical user-id's as well. and the name field is not practical as it contains spaces, and the entry may be long.

comment:12 in reply to: ↑ 11 Changed 7 years ago by anonymous

I think there are multiple steps and some are low hanging fruits while others are note.

I could imagine that on the display site it's just one single function that renders a user's display name (whatever that may be) on every page.

The questions is where the implementation comes from. I could imagine that a simple one just uses the login id or the entered user name. A more advanced one could be provided by a plug-in.

Another step is making the user selection/search more flexible by allowing substring/wild card matches against the user info and not only the login id. However, I don't think that this must be necessarily solved together with this bug. It should be probably tracked in a separate bug.

comment:13 Changed 7 years ago by ThurnerRupert

marked #5692 as duplicate.

comment:14 Changed 7 years ago by ThurnerRupert

see also #2456

comment:15 Changed 6 years ago by d.grellscheid@…

  • Cc d.grellscheid@… added

comment:16 Changed 6 years ago by anonymous

  • Milestone changed from 0.12 to 1.0

comment:17 Changed 6 years ago by anonymous

  • Milestone changed from 1.0 to 0.12

comment:18 Changed 6 years ago by nkantrowitz

A simpler solution to this is just handle the translation in your IAuthenticator.

comment:19 Changed 6 years ago by jeremyk@…

  • Cc jeremyk@… added

we'd love to see this functionality as well. I'm trying to implement it as a hack in the local templates/site.html but still trying to wrap my head around the templates and whatnot :)

We aren't overly concerned with the searching stuff, as mostly we just search by content rather than owner, and owners know their login names, just not everyone else's. It would make it a whole lot easier though for our tech support folks to be able to assign tickets to the admin/dev team by name rather than by our weird login names :)

comment:20 Changed 5 years ago by cboos

See also #7339.

Once we have the possibility to show either full name or login name for user names, we could as well add a third possibility (nicknames), provided we have a way to manage this extra field.

comment:21 Changed 5 years ago by Ryan Ollos <ryano@…>

  • Cc ryano@… added

comment:22 Changed 4 years ago by itamaro

  • Cc itamarost@… added
  • Keywords user added

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as new The owner will remain jonas.
as The resolution will be set. Next status will be 'closed'.
The owner will be changed from jonas to anonymous. Next status will be 'assigned'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.