Content
View differences
Updated by Niels Lindenthal over 2 years ago
#### Problems with this settings
* It adds a lot of complexity for development.
* It is unclear if there is anyone really using it.
* The feature simply does not work.
* There is no differentiation between project, work package, types and status.
* It is not possible to set the field remaining work
<img class="op-uc-image op-uc-image_inline" style="width:1089px;" src="/api/v3/attachments/88613/content">
**Migrations** **Acceptance criteria**
* Case 1: Work is defined -> The Remaining work is derived from % Complete
* Case 2: Work is not defined -> % Complete is deleted (since there is no value for Remaining work
* The aggregated values for the parents are re-calculated.
* There is a journal in the work package explaining the change
* We have tested the performance of migrations in large installations before the release and the deployments.
* It adds a lot of complexity for development.
* It is unclear if there is anyone really using it.
* The feature simply does not work.
* There is no differentiation between project, work package, types and status.
* It is not possible to set the field remaining work
<img class="op-uc-image op-uc-image_inline" style="width:1089px;" src="/api/v3/attachments/88613/content">
**Migrations**
* Case 1: Work is defined -> The Remaining work is derived from % Complete
* Case 2: Work is not defined -> % Complete is deleted (since there is no value for Remaining work
* The aggregated values for the parents are re-calculated.
* There is a journal in the work package explaining the change
* We have tested the performance of migrations in large installations before the release and the deployments.