Content
View differences
Updated by Henriette Darge over 2 years ago
Taken from <mention class="mention" data-id="32764" data-type="work_package" data-text="#32764">#32764</mention> , see there for current requirements
> * There will be two default views in the Gantt sidebar menu
> * "All open"
> * Filters:
> * **Status: open**
> * Display mode: Hierarchy
> * Columns: The same as the default was for the "Gantt chart" default **(project)** view
> * Sort via start date
> * The timeline labels will be: startDate (left), dueDate (right), subject (farRight) consist of:
> * "Gantt overview"
> * Filters:
> * **Type: Type: Milestone, phase** phase
> * Display mode: Hierarchy
> * Columns: The same as the default was for the "Gantt chart" default view
> * Sort via start date
> * The timeline labels will be: startDate (left), dueDate (right), subject (farRight)
> * **OPEN:** Clicking on the menu entry "Gantt" will lead to the "Gantt overview"?
> * The global default **(global)** view will have an additional _Project_ column after ID (like in the Work packages module)
> * This **cannot** be changed in the administration
**Technical note:**
we agreed together with the product team that it is acceptable to solve this via query props that are passed. We accept, that the save icon will then be shown per default
> * There will be two default views in the Gantt sidebar menu
> * "All open"
> * Filters:
> * **Status: open**
> * Display mode: Hierarchy
> * Columns: The same as the default was for the "Gantt chart" default
> * Sort via start date
> * The timeline labels will be: startDate (left), dueDate (right), subject (farRight)
> * "Gantt overview"
> * Filters:
> * **Type:
> * Display mode: Hierarchy
> * Columns: The same as the default was for the "Gantt chart" default view
> * Sort via start date
> * The timeline labels will be: startDate (left), dueDate (right), subject (farRight)
> * **OPEN:** Clicking on the menu entry "Gantt" will lead to the "Gantt overview"?
> * The global
> * This **cannot** be changed in the administration
**Technical note:**
we agreed together with the product team that it is acceptable to solve this via query props that are passed. We accept, that the save icon will then be shown per default