Content
View differences
Updated by Jens Ulferts over 1 year ago
**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 ###41097. With ###56909 developed, the use cases have changed.
## **Acceptance criteria**
**Of the acceptance criteria of ###41097 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 ###41097 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>
**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 ###41097. With ###56909 developed, the use cases have changed.
## **Acceptance criteria**
**Of the acceptance criteria of ###41097 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 ###41097 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>