Content
View differences
Updated by Niels Lindenthal almost 2 years ago
**As an** OpenProject user **Current situation**
**I want to** identify * Installation with 13k+ users, name format set to "last name first name", users synchronized via ldap groups
* For users with the user I want same name, e.g. "Peter Schmitz", it is not possible to select
**So that** I don't select determine which group / department they belong to before adding them to projects
* Although #55602 makes it possible to subsequently check the group membership, it is not very practical, as adding users to projects just to check their group membership may generate notifications for the wrong user, e.g. when managing project members, sharings people, causing confusion and group memberships. support effort
**Implementation sketch**
**Background information about * (Possibly add more fixed attributes to the underlying information**
user)
* There are very large OpenProject installations with > 10 k users. Provide a configuration to allow which field/fields to show next to users in the application
* Show this infomration next to users:
* In those large installations the chances of redundant names increases.
member autocompleter
* This imposes In the risk to select invitation flow
* In work package assignee or user selection autocompleters
* In the wrong users.
**Acceptance criteria** activity stream
Basic mockup:
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/115353/content">
**Group display proposal**
* The row group membership of users should be displayed in the user selection (NG-select) shows drop-down field "Add user" in the user's name and members module (below the user's email. user name)
* The email This is only shown if limited to the user has member invitation flow, and it's not activated possible to identify the setting in "My Account" -> "Hide my email address". important groups to show. For some users such as myself, information will be arbitrarily cut off
* We start with places which allows to select from all users (instead of places where only project members can <img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/114077/content">
**Additional info**
* Alternatively, a freely selectable ldap attribute could be selected):
displayed
* Select Places where displaying the group membership or other distinguishing features may also be useful (but not that relevant, as the probability of names being the same among the members of a project members
is rather unlikely):
* Share work packages
Work Packages
* Share project lists
Assignee
* Select group members
Accountable
* Add user modal
Watchers
* ...
Sharing
* Extending the API to provide this information so all NG select can query those user attributes.
**Out of scope for now**
Boards
* Showing group memberships.
Team Planer
* Adding new user attributes such organization, team and department.
Meetings
* Syncing new attributes from the LDAP. ...
**I want to** identify
* For users with
**So that** I don't select
* Although #55602 makes it possible to subsequently check
**Implementation sketch**
**Background information about
*
*
* In work package assignee or user selection autocompleters
* In
**Acceptance criteria**
Basic mockup:
**Group display proposal**
* The email
* We start with places which allows to select from all users (instead of places where only project members can
**Additional info**
* Alternatively, a freely selectable ldap attribute could
**Out of scope for now**