# Feature OP-17572 - Add a global role to allow custom fields edit

Project: OpenProject
Status: new
URL: https://community.openproject.org/work_packages/OP-17572

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | Wish List |
| Sprint |  |
| Backlog bucket |  |
| Votes | 2 |
| 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 | Administration / Roles and permissions / Global roles and permissions, Administration / Custom fields |
| Feature Flag |  |
| Requires doc change | No |
| Enterprise plan |  |

## Details

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

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Feature Lead |  |
| Developers |  |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

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

## Description

**As** a Administrator  
**I want to** make possible for other selected users to edit custom fields  
**so that** the user does not need to ask an admin to add an option to custom field of type list (exemple a new client entry on a list of customers)

**Acceptance criteria**

*   Global role to edit custom fields
    
*   Optional : more fine grained control to select which type of custome field can be edited (wp, project, user, ....)
    

**Technical notes**

*   similar to global role to modify text help attribute
    

**Out of scope**

*   Add options to custom fields of type `List` via the openproject API
    

<br>
