# Feature AUTOWORK-418 - Project Administration for contextualization of list/hierarchy custom fields

Project: Stream Workflows & Automations
Status: in review
URL: https://community.openproject.org/work_packages/AUTOWORK-418

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | 18.1.0 |
| Sprint |  |
| Backlog bucket |  |
| Votes |  |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Use cases

_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 | Enterprise / Professional (PRO) |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups |  |
| Build Number |  |
| Found in mobile app version |  |
| Follow-up feedback e-mail |  |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee | Oliver Günther |
| Accountable |  |
| Product manager | Sonita Soth |
| Feature Lead | Klaus Zanders |
| 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** a project admin  
**I want to** choose which values of a custom field my project uses and add values that only my project needs, as far as the global administrator allows it  
**so that** my team works with values that fit the project without asking a global administrator for every change

## Acceptance criteria

_Project settings › Work packages › Custom fields_

*   The table lists the custom fields used by the work packages of the project with the columns &quot;Custom field&quot;, &quot;Format&quot; and &quot;Displayed in type&quot;.
    
*   &quot;Displayed in type&quot; lists the types and variants that include the field. They link to the Types tab of the project settings if the user may manage types or project variants. Otherwise they are plain text.
    
*   Fields of the formats list, hierarchy and weighted item list link to their values page if the user has the permission &quot;Manage work package custom field values&quot;.
    
*   The row shows how many project-specific values the project has for that field.
    

_Values of a custom field in the project settings_

*   The page is always accessible with the permission for list, hierarchy and weighted item list fields used in the project, regardless of the field&#x27;s settings.
    
*   The page shows the list &quot;Available values&quot;. Hierarchies show the short name of each value in its row, weighted item lists the weight. Project-specific values carry the project-specific label after them.
    
*   The explanation &quot;Choose which values of {custom field} your team can use in {project} …&quot; is only shown if the user can activate values or add values.
    

_Activating values_

*   If the field uses the Allow filter or the Block filter, each global value has a toggle when:
    
    *   the user is a global admin, or
        
    *   &quot;Project admins can manage values at a project level&quot; is on.
        
*   With the toggles, &quot;Enable all&quot; and &quot;Disable all&quot; are offered as well.
    
*   If the user cannot activate values, the list only shows the values available in the project.
    
*   A global value that is the parent of an available project value cannot be deactivated. The row explains: &quot;Cannot be disabled because a child project-specific value is enabled&quot;.
    
*   Adding a project value below a global value activates the global value and its parents.
    

_Adding and editing values_

*   If &quot;Project admins can add project-specific values&quot; is on, the user can add values to the project and edit the values of the project. Global values cannot be edited here.
    
*   The dialog states the project in bold: &quot;Only available in **{project}**.&quot;
    
*   For hierarchies, the short name has the caption &quot;Optionally pick a shorter name or code for this value.&quot;
    
*   For weighted item lists, the weight is required and has the caption &quot;Each value has a weight associated with it.&quot;
    
*   The parent options match the list on the page: all values if the user can activate values, otherwise only the values available in the project.
    

_Deleting values_

*   Global admins and users with the permission can always delete the values of their project, even if &quot;Project admins can add project-specific values&quot; is off.
    
*   The last value of a custom field cannot be deleted. The page shows an error message instead.
    

_Making values global_

*   Only global admins can convert a project value to a global one from this page. A message confirms the result.
    

_Details tab of a custom field_

*   When projects already have project-specific values and &quot;Project admins can add project-specific values&quot; is unchecked, a warning shows how many projects and values are affected. It says that these values remain available in their projects. The warning appears and disappears as the option is toggled.
    

## Technical notes

*   The project settings page and the Projects tab of the global administration share one controller concern (`CustomFields::ProjectSpecificValueActions`). Each controller provides the custom field, the project and the paths.
    
*   The create, update and delete contracts of list options and hierarchy items allow project values for users with `manage_work_package_custom_field_values` in that project.
    
*   Creating and updating additionally require &quot;Project admins can add project-specific values&quot;. Deleting does not.
    

## Permissions and visibility considerations

*   _To whom is this feature visible?_
    
    *   Users with the new project permission &quot;Manage work package custom field values&quot; (Work packages module, requires membership).
        
    *   What they can do on a values page depends on the settings of the custom field, as described above.
        
    *   Global administrators, who can always activate values when the Allow filter or the Block filter is used, and who can make project values global.
        
    *   The feature requires the Enterprise feature &quot;Project-specific values for custom fields&quot;.
        
*   _When is it not visible?_
    
    *   For users without the permission. They see the custom fields without links to their values.
        
    *   For custom fields of other formats and for custom fields the project does not use.
        

## Translation considerations

*   Key terms and phrases:
    
    *   &quot;Manage work package custom field values&quot;
        
    *   &quot;Available values&quot;
        
    *   &quot;Displayed in type&quot;
        
*   With the toggles, &quot;Enable all&quot; and &quot;Disable all&quot; are offered as well.
    
*   If the user cannot activate values, the list only shows the values available in the project.
    
*   A global value that is the parent of an available project value cannot be deactivated. The row explains: &quot;Cannot be disabled because a child project-specific value is enabled&quot;.
    
*   Adding a project value below a global value activates the global value and its parents.
