Content
View differences
Updated by Eric Schubert over 1 year ago
**As** an OpenProject administrator
**I want to** interact with the custom fields administration
**so that** I can create new custom fields of type hierarchy or edit existing ones.
**Acceptance criteria**
* On `/custom_fields/new?type=WorkPackageCustomField` the format dropdown contains the option "Hierarchy".
* When creating a custom field of type hierarchy we need to be able to set the following options:
* "Name" - Required, String
* "Allow multi-select" - Checkbox
* "Required" - Checkbox
* "For all projects" - Checkbox
* "Used as a filter" - Checkbox
* "Searchable" - Checkbox
* When the user clicks on "Save", the custom field details view is shown.
* ⚠️ the current behaviour redirect to custom fields index page. Can we change that for this custom field?
* The custom field details view has two sub pages (tabs)
* Details
* The "Details" view shows the following options:
* "Name" - Required, String
* "Allow multi-select" - Checkbox
* "Required" - Checkbox
* "For all projects" - Checkbox
* "Used as a filter" - Checkbox
* "Searchable" - Checkbox
* Values
* The "Values" view shows a placeholder for the empty values after creation.
* The user must be able to create new values.
* The user must be able to assign a label and a short to a new value.
* The user is not allowed to create a value with a label or a short that already exists on that level.
* The user must be able to submerge into a value to create child values.
* The user must be able to delete a value.
* Deletion of a value deletes all sub values.
* The user must be able to edit a value.
* If the user submerged into any value, a breadcrumb with the ancestors must be displayed. The user must be able to go to any of the current ancestors.
**Important hints**
* A deletion eventually is possible as hard or soft delete.
* The first iteration only supports hard delete.
* A soft delete marks a value and all descendants as deleted, but does not remove the entity from the database.
* A sorting is planned, hence the data model must support an order of values of the same level.
**I want to** interact with the custom fields administration
**so that** I can create new custom fields of type hierarchy or edit existing ones.
**Acceptance criteria**
* On `/custom_fields/new?type=WorkPackageCustomField` the format dropdown contains the option "Hierarchy".
* When creating a custom field of type hierarchy we need to be able to set the following options:
* "Name" - Required, String
* "Allow multi-select" - Checkbox
* "Required" - Checkbox
* "For all projects" - Checkbox
* "Used as a filter" - Checkbox
* "Searchable" - Checkbox
* When the user clicks on "Save", the custom field details view is shown.
* ⚠️ the current behaviour redirect to custom fields index page. Can we change that for this custom field?
* The custom field details view has two sub pages (tabs)
* Details
* The "Details" view shows the following options:
* "Name" - Required, String
* "Allow multi-select" - Checkbox
* "Required" - Checkbox
* "For all projects" - Checkbox
* "Used as a filter" - Checkbox
* "Searchable" - Checkbox
* Values
* The "Values" view shows a placeholder for the empty values after creation.
* The user must be able to create new values.
* The user must be able to assign a label and a short to a new value.
* The user is not allowed to create a value with a label or a short that already exists on that level.
* The user must be able to submerge into a value to create child values.
* The user must be able to delete a value.
* Deletion of a value deletes all sub values.
* The user must be able to edit a value.
* If the user submerged into any value, a breadcrumb with the ancestors must be displayed. The user must be able to go to any of the current ancestors.
**Important hints**
* A deletion eventually is possible as hard or soft delete.
* The first iteration only supports hard delete.
* A soft delete marks a value and all descendants as deleted, but does not remove the entity from the database.
* A sorting is planned, hence the data model must support an order of values of the same level.