Content
View differences
Updated by Jonas Jabari about 2 years ago
### Acceptance Criteria
* There is a new entry in the Project settings called "Project attributes"
* All project custom fields These are listed in boxes, grouped by their sections in just notes to facilitate the same order as defined implementation. The authoritative specification is in the global admin page ((visible setting <mention class="mention" data-id="49688" data-type="work_package" data-text="#49688">#49688</mention>
(Note: `Project Attributes` is respected, only admins can see/enable/disable "invisible" project attributes)
* The order of section/attributes cannot be changed here
* The project attributes are shown with their name, type and a badge "required" if they are required
* Each project attribute can be enabled/disabled (activated/deactivated) new name for the current project using the toggle switch (except required ones)
* The toggle switch is disable for required project attributes (in the on position)
* No extra confirmation is shown after using the toggle switch
* The "enable all"/"disable all" buttons per section allow bulk actions in order to mass edit the activation state existing concept of project attributes
`Project Custom Fields`)
### Acceptance criteria
* Required Enable/disable project attributes always stay activated and are not affected by the bulk edit buttons
* No extra confirmation is shown after using the mass edit buttons
* Disabling a project attribute does _not_ delete an assigned custom value
* A disabled fields on project attribute and its custom value:
* Will not be shown in the level via new project overview settings page sidebar (specs below)
* Will not be exported (specs below)
* Cannot be targeted by a filter in the project list (specs below)
* For more convenience, the list can be filtered by project attribute name Add client-side filtering and type via search input below the header
buld-edits on this UI for better UX
### Technical notes
* When a filter is active, the bulk edit buttons are hidden
* URL routing: `projects/{project_id}/settings/project_custom_fields`
* Accessible to project members with the permission "select\_project\_custom\_fields" Introduce mapping table `custom_fields` <-> `projects`
* There is a new entry in the Project settings called "Project attributes"
* All project custom fields
(Note: `Project Attributes`
* The order of section/attributes cannot be changed here
* The project attributes are shown with their name, type and a badge "required" if they are required
* Each project attribute can be enabled/disabled (activated/deactivated)
* The toggle switch is disable for required project attributes (in the on position)
* No extra confirmation is shown after using the toggle switch
* The "enable all"/"disable all" buttons per section allow bulk actions in order to mass edit the activation state
### Acceptance criteria
* No extra confirmation is shown after using the mass edit buttons
* Disabling a project attribute does _not_ delete an assigned custom value
* A disabled
* Will not be shown in the
* Will not be exported (specs below)
* Cannot be targeted by a filter in the project list (specs below)
* For more convenience, the list can be filtered by project attribute name
### Technical notes
* URL routing: `projects/{project_id}/settings/project_custom_fields`
* Accessible to project members with the permission "select\_project\_custom\_fields"