Content
View differences
Updated by Niels Lindenthal almost 2 years ago
### 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
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
checked
### What is the expected behavior?
1. If "For all projects" has not been checked, CF should not be enabled everywhere.
### Environment information
**OpenProject installation type**
* [ ] Hosted cloud edition
* [ ] Packaged installation
* What distribution?
* [ ] Docker All-in-one container
* [ ] Docker-compose installation
* [x] Other (please specify): QA Edge 12.5.0
1. Login to QA Edge
* Custom field is automatically active in all projects although "For all projects" has not been checked
1. If "For all projects" has not been checked, CF should not be enabled everywhere.
### Environment information
**OpenProject installation type**
* [ ] Hosted cloud edition
* [ ] Packaged installation
* What distribution?
* [ ] Docker All-in-one container
* [ ] Docker-compose installation
* [x] Other (please specify): QA Edge 12.5.0