# Epic AUTOWORK-300 - Contextualization of custom fields: Define values for custom field of type hierarchy on a work-package-type-basis

Project: Stream Workflows & Automations
Status: new
URL: https://community.openproject.org/work_packages/AUTOWORK-300

## Detailed specification

### Motivation and background information

Choose which values of a custom field of type hierarchy can be used for which work package type. This builds on the project-basis Epic <mention class="mention" data-id="53806" data-type="work_package" data-text="#AUTOWORK-283" data-display-id="AUTOWORK-283">\#AUTOWORK-283</mention> , where the global admin already chooses which values each project can use.

Example: A priority field could have different values for Tasks than for Bugs.

**To clarify:**

  - If the project and the type do not agree (a value is on for the project but off for the type, or the other way around), which one wins?

  - Is this the same permission as in <mention class="mention" data-id="53806" data-type="work_package" data-text="#AUTOWORK-283" data-display-id="AUTOWORK-283">\#AUTOWORK-283</mention> ?

  - Does the project admin turn values off for a type only in their own project, or for the type everywhere?

  - Where does the global admin set this? Our idea is the form configuration of the work package type.

### Acceptance criteria

1.  The global admin can turn single values of a custom field on or off for a work package type.
    
2.  On a work package, users can only pick the values that are turned on for its type.
    
3.  The setting is part of the form configuration of the work package type.
    
4.  The global admin can set a permission that decides if project admins may limit values per work package type.
    
5.  Project admins without this permission cannot change the selection.
    
6.  A project admin with the permission sees the values the type has and can turn some of them off for their project.
    
7.  Values turned off by the project admin can no longer be picked for this type in this project.
    
8.  The project admin cannot turn on values that the global admin did not give to the type.

### Out of scope

| Attribute | Value |
| --- | --- |
| Mockups |  |

## Planning

| Attribute | Value |
| --- | --- |
| Roadmap | 2027 Q3 |
| Date |  |
| Votes |  |
| List |  |
| Target versions |  |
| Sprint |  |
| Backlog bucket |  |
| Relevance |  |

## Subitems

_No work packages_

## Bugs and other work packages

_No work packages_

## Details

| Attribute | Value |
| --- | --- |
| Module |  |
| Enterprise plan |  |
| Labels |  |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager | Sonita Soth |
| Designer | Parimal Satyal |
| Developers | OP Dev Sirius Team |
| Requested by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| Work |  |

## Description

**Jobs to be done**

*   **Global admin:** If a work package type needs only some of the values, I want to limit which values can be picked for this type. Then I only maintain the list once, and every type only shows what it needs.
    
*   **Project admin:** If a work package type in my project needs only some of the values, I want to turn off the others, so my team has fewer options to choose from.
    
*   **End user:** When I set a value on a work package, I only want to see the values that fit my project and my work package type. Then I can find the right one fast and make fewer mistakes.
    

**User Story**

1.  As a global admin, I want to limit values per work package type, so that a type only shows the values that matter for it.
    
2.  As a global admin, I want to control with a permission whether project admins are allowed to limit values per work package type in their project, so that I decide who can change the selection.
    
3.  As a project admin, I want to turn off some of the values for a work package type in my project, so that my team only sees the values that matter for this type.