Content
View differences
Updated by Henriette Darge almost 7 years ago
### Current setup
* The admin section has many menu entries on the left, making it hard to find any content
* Some settings are distributed over multiple entries (e.g. System settings, plugin settings, and own menu entry)
* A **pragmatic** solution is to make use of the two level menu we already have in the application.
* When collecting things that belong together under one menu item, these things are easier to find.
### Expected outcome
* Create a new menu entry **Work Packages** in the admin menu.
* Move the following entries as child entries under the newly create item:
* Work package types (can the be renamed to "types")
* Work package status (can the be renamed to "status")
* Workflow
* Help text attributes (remove the tab layout)
* Custom Actions (?)
* The tab "work package tracking" of the system settings (maybe rename to "Work package settings" ?)
### Out of Scope
* Improvements in the UX (e.g. for workflows) are explicitly out of scope. This contains only restructuring of existing content.
* In contrast to the some of our other two level menus, these views shall not be transferred to an angular view. Thus a page reload will be necessary when switching between the pages (like in the wiki page).
* The admin section has many menu entries on the left, making it hard to find any content
* Some settings are distributed over multiple entries (e.g. System settings, plugin settings, and own menu entry)
* A **pragmatic** solution is to make use of the two level menu we already have in the application.
* When collecting things that belong together under one menu item, these things are easier to find.
### Expected outcome
* Create a new menu entry **Work Packages** in the admin menu.
* Move the following entries as child entries under the newly create item:
* Work package types (can the be renamed to "types")
* Work package status (can the be renamed to "status")
* Workflow
* Help text attributes (remove the tab layout)
* Custom Actions (?)
* The tab "work package tracking" of the system settings (maybe rename to "Work package settings" ?)
### Out of Scope
* Improvements in the UX (e.g. for workflows) are explicitly out of scope. This contains only restructuring of existing content.
* In contrast to the some of our other two level menus, these views shall not be transferred to an angular view. Thus a page reload will be necessary when switching between the pages (like in the wiki page).