Content
View differences
Updated by Klaus Zanders about 2 months ago
**As** a resource planner
**I want to** know the job title of a user and their key skills
**so that** I can properly assign resources to work packages
**Acceptance criteria**
* Additional user information will be tracked with **User Custom Fields**
* For this, Administrators need to Application administrators can manage items selectable in the layout of the user form management (like Time tracking activities, Priorities)
* The user custom field management is moved as a menu item in In the Users & Permissions section in the administration Administration an application administrator can define Job Roles (i.e. Software Developer, Designer, QA, etc)
* User custom fields are grouped into sections
In the Administration an application administrator can define Key Skills (i.e. Ruby On Rails, React, Angular, etc)
* Additionally to In the custom fields, the built-in fields (first name, last name, email, department, etc) are listed user settings there as well and can should be re-arranged in fields for setting
* the form.
users job role (single select)
* When editing or showing the user profile, users key skills (multi select)
* the data/form is displayed as configured by the admin
users manager (user select)
* A user custom field also gets a boolean if that info should The data needs to be shown in editable via the user information card. If this is checked, the custom field is also shown whenever user details are displayed (see Figma for details)
* Hierarchy custom fields are also available for user custom fields API
**Technical notes**
* <br> We do not want to allow free text as this will make it very bad to find resources matching anything.
**Permissions and visibility considerations**
* There should probably be a setting if users can edit this themselves? This needs to be discussed
**Translation considerations**
* _Key terms and phrases in the key languages_ languages_
**Out of scope**
* <br>
_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._
**I want to** know the job title of a user and their key skills
**so that** I can properly assign resources to work packages
**Acceptance criteria**
* Additional user information will be tracked with **User Custom Fields**
* For this, Administrators need to
* The user custom field management is moved as a menu item in
* User custom fields are grouped into sections
*
*
* Hierarchy custom fields are also available for user custom fields
**Technical notes**
* <br>
**Permissions and visibility considerations**
* There should probably be a setting if users can edit this themselves? This needs to be discussed
**Translation considerations**
* _Key terms and phrases in the key languages_
**Out of scope**
* <br>
_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._