Content
View differences
Updated by Jens Ulferts about 1 year ago
**As** an administrator
**I want to** enforce having custom fields filled when creating a project, a work package, a time entry, ...
**so that** I can enforce a process
**As** a person modifying a project, work package, time entry, ...
**I want to** still be able to update a project, work package, time entry, ... without having to provide a value
**so that** I can change the object and not be blocked
**Cases where required custom fields are currently problematic**
* Updating a project via the settings page (after ###61889)
* ###63668
* ###62563
* Updating work packages via the table
* Updating work packages on the full/split view
* Updating a time entry?
* Updating a user?
* Changing the user's password?
**Acceptance criteria**
* Filling a required custom field is not enforced on updating existing objects:
* Projects
* Work packages
* Time entry
* Versions
* Users
* Groups
* Setting a required custom field to null on an existing object is not possible.
* In the custom field administration, the "Required" field caption states: "_Mark the custom field as required. This will make it mandatory to fill in the field when creating new resources. Existing resources will not require to have the field set on their next update."_
**Technical notes**
* <br>
**Permissions and visibility considerations**
* No changes in permission
**Translation considerations**
* _Key terms and phrases in the key languages_
**Out of scope**
* <br>
**I want to** enforce having custom fields filled when creating a project, a work package, a time entry, ...
**so that** I can enforce a process
**As** a person modifying a project, work package, time entry, ...
**I want to** still be able to update a project, work package, time entry, ... without having to provide a value
**so that** I can change the object and not be blocked
**Cases where required custom fields are currently problematic**
* Updating a project via the settings page (after ###61889)
* ###63668
* ###62563
* Updating work packages via the table
* Updating work packages on the full/split view
* Updating a time entry?
* Updating a user?
* Changing the user's password?
**Acceptance criteria**
* Filling a required custom field is not enforced on updating existing objects:
* Projects
* Work packages
* Time entry
* Versions
* Users
* Groups
* Setting a required custom field to null on an existing object is not possible.
* In the custom field administration, the "Required" field caption states: "_Mark the custom field as required. This will make it mandatory to fill in the field when creating new resources. Existing resources will not require to have the field set on their next update."_
**Technical notes**
* <br>
**Permissions and visibility considerations**
* No changes in permission
**Translation considerations**
* _Key terms and phrases in the key languages_
**Out of scope**
* <br>