Skip to content

Commit

Permalink
Apply suggestions from code review
Browse files Browse the repository at this point in the history
Co-authored-by: dominic-braeunlein <[email protected]>
  • Loading branch information
MayaBerd and dominic-braeunlein authored Oct 8, 2024
1 parent 196315f commit 2091de5
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions docs/system-admin-guide/custom-fields/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -45,14 +45,14 @@ Depending on the module, for which the new custom field is being created, sligh

> [!IMPORTANT]
>
> Custom fields need to be activated per work package type and added to project(s). Work package custom fields are only visible when two conditions are met:
> Custom fields need to be activated per work package type and added to a project. Work package custom fields are only visible when two conditions are met:
>
> 1. Custom field has been added to the work package type (form configuration).
> 2. Custom field is activated for a single or multiple projects.
> 2. Custom field is activated for the project.
### Assign a custom field to a work package type (Enterprise add-on)

You can[assign a custom field to a work package type](../manage-work-packages/work-package-types/#work-package-form-configuration-enterprise-add-on) (Form configuration) directly via the link in the custom field overview.
You can [assign a custom field to a work package type](../manage-work-packages/work-package-types/#work-package-form-configuration-enterprise-add-on) (form configuration) directly via the link in the custom field overview.

![Add a custom field to a work package type](system-admin-add-field-to-wp-type.png)

Expand Down

0 comments on commit 2091de5

Please sign in to comment.