Content
View differences
Updated by Jens Ulferts about 6 years ago
### Acceptance criteria
* There is an indication about the active scheduling mode per work package in the list.
* **Assumption:** the indication is a column the user can display/hide same as every other column
* The scheduling mode can be altered within the list
* **Open**: How is the mode switch handled? Assumption: The user clicks on the icon to activate, then selects the mode. This will require two clicks but prevents accidental changes.
* The column is not to be included when printing
### Open
* Can the user choose to hide/display the "mode" column same as every other column?
* If the column can be hidden/displayed by the user:
* What is the default?
* Is the information whether the column is hidden/displayed stored together with the query?
* Do we alter the default for existing installations to promote the new feature?
* Can the default be altered via the settings same as the other columns?
* How is the mode switch handled (UX)? Some screens would be helpful.
* Which icons to use?
### Out of scope
* TBD
### Implementation notes
* Mostly depends on the open questions.
* In case the mode is handled same as every other column it needs to be stored with the query as a column. We then need to extend the available columns in the API and potentially also the query object.
* There is an indication about the active scheduling mode per work package in the list.
* **Assumption:** the indication is a column the user can display/hide same as every other column
* The scheduling mode can be altered within the list
*
* The column is not to be included when printing
### Open
* Can the user choose to hide/display the "mode" column same as every other column?
* If the column can be hidden/displayed by the user:
* What is the default?
* Is the information whether the column is hidden/displayed stored together with the query?
* Do we alter the default for existing installations to promote the new feature?
* Can the default be altered via the settings same as the other columns?
* How is the mode switch handled (UX)? Some screens would be helpful.
* Which icons to use?
### Out of scope
* TBD
### Implementation notes
* Mostly depends on the open questions.
* In case the mode is handled same as every other column it needs to be stored with the query as a column. We then need to extend the available columns in the API and potentially also the query object.