Content
View differences
Updated by Jens Ulferts about 1 year ago
**As** an a administrator
**I want to** enforce having custom fields filled be be prompted to set a value for all work packages that are in an invalid state when creating a project, required field is newly activated in a work package, a time entry, ... project
**so that** I can enforce a process avoid invalid states which blocks users from updating WPs
**As** **Possibilities to create an invalid WP state**
* **Instance level**
* Custom Field Admin
* Create required CF and add it to a person modifying project and a project, work package, time entry, ...
**I want to** still be able to update package type
* Change a project, work package, time entry, ... without having existing field to provide required
* Mark a value
**so that** I can change the object and not be blocked
**Cases where required custom fields are currently problematic**
field "For all projects"
* Updating Add a required field to a project via the settings page (after ###61889)
* ###63668
<img class="image_resized op-uc-image op-uc-image_inline" style="width:321px;" src="/api/v3/attachments/470241/content">
* ###62563
Custom Field Items
* Updating work packages via the table
Remove item in list or hierarchy that are selected
* Updating work packages on the full/split view
<img class="image_resized op-uc-image op-uc-image_inline" style="width:396px;" src="/api/v3/attachments/470242/content">
* Updating a time entry?
Work Package Type Admin
* Updating a user?
Chance form configuration and add required CF to form
* Changing the user's password?
**Acceptance criteria**
* Filling a required (Add custom field is not enforced on updating existing objects:
to subject pattern)
* Projects
<img class="image_resized op-uc-image op-uc-image_inline" style="width:337px;" src="/api/v3/attachments/470243/content">
* **Project level**
* Work packages Package Type setting
* Time entry
Activate required custom fields for project
* Versions
<img class="image_resized op-uc-image op-uc-image_inline" style="width:454px;" src="/api/v3/attachments/470244/content">
* Users
FYI: Required Project Attributes can not be deactivated on project level
* Groups
Moving WP to other project when other required CFs are enabled
* In the custom field administration, the "Required" field caption states: "_Mark the custom field as required. This will make it mandatory No issue and stops action with error. WP can't be moved to fill in the field another project when creating new resources. Existing resources will not require to have no value is selected
<br>
**Acceptance criteria**
* Idea:
* Show modal and let admin choose a value that is set for all relevant WPs
* (What is the field set on their next update."_
idea behind required then?)
**Technical notes**
* <br>
**Permissions and visibility considerations**
* No changes in permission _To whom is this feature visible?_
* _When is it not visible?_
**Translation considerations**
* _Key terms and phrases in the key languages_ languages_
**Out of scope**
* <br>
**I want to** enforce having custom fields filled
**so that** I can enforce a process
**As**
* **Instance level**
* Custom Field Admin
* Create required CF and add it to
**I want to** still be able to update
* Change
* Mark
**so that** I can change the object and not be blocked
**Cases where required custom fields are currently problematic**
**Acceptance criteria**
* Filling a required
*
* Time entry
<br>
**Acceptance criteria**
* Idea:
* Show modal and let admin choose a value that is set for all relevant WPs
* (What is
* <br>
**Permissions and visibility considerations**
* No changes in permission
* _When is it not visible?_
**Translation considerations**
* _Key terms and phrases in the key languages_
**Out of scope**
* <br>