Content
View differences
Updated by Christophe Bliard over 2 years ago
When the statuses are created, they do not have any % Complete value by default. This makes the "% Complete by status" mode inoperant until the user manually and tediously sets the % Complete values See ##40867 for each status.
This work package sets default values for the seeded work package status full picture.
* Add Change seeding to set % Complete values to seeded created statuses
* Standard edition Update closed statuses to always have 100%. This is consistent with previous behavior where all closed statuses (including rejected) is considered 100% complete in the computation.
* New: 0%
* In specification: 10%
* Specified: 15%
* Confirmed: 20%
* To be scheduled: 25%
* Scheduled: 30%
* In progress: 50%
* Developed: 70%
* In testing: 80%
* Tested: 90%
* Test failed: 75%
* Closed: Is it desirable? Are there good reasons not to have 100% completion for all closed statuses?
* On hold: 30%
* Rejected: 0%
* BIM edition
* New: 0%
* In progress: 40%
* Resolved: 80%
* Closed: 100% we'll see later about how to exclude some statuses like rejected
This work package sets default values for the seeded work package status
* Add
* Standard edition
* New: 0%
* In specification: 10%
* Specified: 15%
* Confirmed: 20%
* To be scheduled: 25%
* Scheduled: 30%
* In progress: 50%
* Developed: 70%
* In testing: 80%
* Tested: 90%
* Test failed: 75%
* Closed:
* On hold: 30%
* Rejected: 0%
* BIM edition
* New: 0%
* In progress: 40%
* Resolved: 80%
* Closed: 100%