Content
View differences
Updated by Niels Lindenthal about 2 years ago
**As** an administrator
**I want to** activate and deactivate a custom field, type or storage providers in the administration
**so that** I don't have to go to the project settings of each project to activate and deactivate them separately.
**Acceptance criteria**
* There is a new tab "Projects" in the following views:
* Administration -> Project Attributes -> _<Project attribute A>_
* Administration -> Custom fields -> Work packages -> _<Custom field A>_
* Administration -> Work packages -> Type -> _<Type A>_
* Administration _->_ Storages _-> <Storages A>_
* In the tab "Projects" all projects are listed where the custom field/project attribute is activated.
* The list is similar to the existing project list.
* Parent projects which are not active are not shown. This is the similar approach like we do in the project list when a user is not allowed to see all projects.
* For each active project there is an action which allows to deactivate the project, e.g. a button or a checkbox - whatever is easy to implement and complies with Primer.
* Above the list there is a button "select projects".
* It opens a menu similar to the "include projects".
* Filter: All projects | Only selected
* Primary button: Apply
* Secondary button: Clear selection
* Checkbox: Include all sub projects
* Bulk action: "Select all" and "Unselect all" (projects)
**I want to** activate and deactivate a custom field, type or storage providers in the administration
**so that** I don't have to go to the project settings of each project to activate and deactivate them separately.
**Acceptance criteria**
* There is a new tab "Projects" in the following views:
* Administration -> Project Attributes -> _<Project attribute A>_
* Administration -> Custom fields -> Work packages -> _<Custom field A>_
* Administration -> Work packages -> Type -> _<Type A>_
* Administration _->_ Storages _-> <Storages A>_
* In the tab "Projects" all projects are listed where the custom field/project attribute is activated.
* The list is similar to the existing project list.
* Parent projects which are not active are not shown. This is the similar approach like we do in the project list when a user is not allowed to see all projects.
* For each active project there is an action which allows to deactivate the project, e.g. a button or a checkbox - whatever is easy to implement and complies with Primer.
* Above the list there is a button "select projects".
* It opens a menu similar to the "include projects".
* Filter: All projects | Only selected
* Primary button: Apply
* Secondary button: Clear selection
* Checkbox: Include all sub projects
* Bulk action: "Select all" and "Unselect all" (projects)