# Feature OP-12015 - Custom field no longer added to all projects when added to a type

Project: OpenProject
Status: closed
URL: https://community.openproject.org/work_packages/OP-12015

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | 15.0.0 |
| Sprint | 15.0.0 |
| Backlog bucket |  |
| 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 | Yes |
| Enterprise plan |  |

## Details

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

## People

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

## Estimates and progress

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

## Description

**As** a project administrator  
**I want to** have a better control when to add custom fields needed for a selected type  
**so that** I don't have to disable custom fields in a lot of projects.

This feature is somewhat of the inverse of <mention class="mention" data-id="41097" data-type="work_package" data-text="###41097">###41097</mention>. With <mention class="mention" data-id="56909" data-type="work_package" data-text="###56909">###56909</mention> developed, the use cases have changed.

## **Acceptance criteria**

**Of the acceptance criteria of <mention class="mention" data-id="41097" data-type="work_package" data-text="###41097">###41097</mention> only case D is supposed to be changed.**

**Case D:** Adding a new custom field to an existing type

When adding new custom fields to a type through the form configuration shown below, the added custom fields will no longer be enabled in all projects that have the type enabled currently.

<figure class="image op-uc-figure"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/34696/content"></div></figure>

**Of the acceptance criteria of <mention class="mention" data-id="41097" data-type="work_package" data-text="###41097">###41097</mention> cases A to C are to remain unchanged:**

  - **Case A:** New project created

  - **Case B:** Adding a type to an existing project

  - **Case C:** Adding a project to a type through administration

## *This feature originally was a bug. The report follows below:*

### Steps to reproduce

1.  Login to QA Edge

2.  Go to Administration -\> Custom fields -\> Create new custom fields

3.  Enter necessary information but leave "For all projects" unchecked

4.  Save the form and add the field to a specific work package type

### What is the buggy behavior?

  - Custom field is automatically active in all projects although "For all projects" has not been checked

### What is the expected behavior?

1.  If "For all projects" has not been checked, CF should not be enabled everywhere.

<br>
