# Feature RESMA-42 - Special roles for User Attributes

Project: Stream Resource Management
Status: closed
URL: https://community.openproject.org/work_packages/RESMA-42

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | 17.7.0 |
| Votes |  |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Features and Chunks

_No work packages_

## Bugs and other work packages

_No work packages_

## Technical Details

| Attribute | Value |
| --- | --- |
| Module |  |
| Feature Flag |  |
| Requires doc change | No |
| Enterprise plan | Community (COM) |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups |  |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Developers | Klaus Zanders |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| PD (min) |  |
| PD (max) |  |
| Work |  |
| Labor costs |  |

## Description

**As** an administrator  
**I want to** mark custom fields with special roles   
**so that** they correctly depict their semantic meaning

**Acceptance criteria**

  - In user attributes there is a new setting where we allow selecting what purpose the field is linked to.

  - First implementation of this is the "job title" field, but we will have other fields in the future (i.e. a user field with purpose "manager" might come to mind)

  - Only one field should be allowed to have the purpose set and a field can only have one purpose

**Technical notes**

  - There should be proper scopes to quickly get the custom field/custom value by the purpose's identifier

**Permissions and visibility considerations**

  - *admin only manageable*