Content
View differences
Updated by Niels Lindenthal over 2 years ago
# Acceptance criteria
* Status can not be connected with a % Complete value (deprecated in #52130)
* "Rejected" children are excluded from the calcuation (#49409)
* If there is no work entered it is not possible to enter a % Complete
* The reason is: An unfinished work package (< 100 %) needs a value before Remaining work. There can not be Remaining work if there is no Work defined. Work.
* The correct calculation is specified in <mention class="mention" data-id="40867" data-type="work_package" data-text="#40867">#40867</mention>
* Remaining work and % Complete can only be entered for a work package that has Work defined
* When creating a new work package work is 0 h \[**open:** unset?\]
* When clicking on on of the attributes (Work, Remaining work, % complete) the modal opens
* In the modal the fields Remaining work and % Complete are deactivated. The field work is active (not mandatory).
* After entering a value to Work, the Remaining work is derived.
* Example: Work 10 h, Remaining work 10 h, % Complete 0%)
* Example: Work 10 h, Remaining work 5 h, % Complete 50%)
* Deleting the field Work deletes % Complete and Remaining Work
**Current (wrong) calcuation 13.2**
<figure class="image op-uc-figure"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/88713/content"></div><figcaption class="op-uc-figure--description">https://niels.openproject-edge.com/projects/progress-calculation-1/work_packages?query_id=338</figcaption></figure>
**Correct calculation**
<figure class="image op-uc-figure"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/88712/content"></div><figcaption class="op-uc-figure--description">https://community.openproject.org/api/v3/file_links/1269/open</figcaption></figure>
###
### Open Questions
* **Migration**: If % complete will necessitate a value for Work, what happens to work package that currently only have a % conmplete without work?
* Eg pre-migration: Work = (unset), % Complete = 75%, Remaining work = (unset)
* Eg post-migrationL Work = ??, % Complete = 75%, Remaining work = ??
* **Closed status:** What happens when a work package is closed? Does % complete go to 100%?
* If so, what do we do if work was not set for that work package?
* **Work by default,** should work be 0h or unset for new work packages or work packages where "work" was not previously input?
* Note: it has to be - for the mechanism where the other two fields (% complete, remaining work) are disabled until a value for work is set.
* What does it mean (semantically) for work to be 0h?
* Does it ever really make sense for Work to be changed by the other two values?
* **Adding work:** What happens if I change the value of work?
* Example 1:
* Initial state: W = 10h, RW = 5h, % = 50%
* Action: Change W to 15h
* Three possible scenarios
* Scenario 1: W = 15h, RW = 5h (unchanged), % = 66,66%
* Scenario 2: W = 15h, RW = 10h, % = 33,33% (work done = unchanged)
* Scenario 3: W = 15h, RW = 7,5h, % = 50% (unchanged)
* Example 2:
* Initial state: W = 10h, RW = 5h, % = 50%
* Action: Change RW to 10h
* Three possible scenarios:
* Scenario 1: W = 10h (unchanged), RW = 10h, % = 0%
* Scenario 2: W = 15h, RW = 10h, % = 33,33% (work done = unchanged)
* Scenario 3: W = 20h, RW = 10h, % = 50% (unchanged)
* Example 3:
* Initial state: W = 0h, RW = 0h, % = 0%
* Action: Change W to 15h
* Result 1: W = 15h, RW = 15h (automatically set) % = 0% (automatically set)
* Is this correct?
* **Base values:** If all three values are interlinked, which of the values should other values pivot around? Which is the "main" value that should not change?
* For example, if work is increased, which one should remain unchanged?
* Remaining work
* % complete
* Work done (which is not visible)
* **Work done** = isn't this a missing field, without which users will have trouble understanding certain "automatic" calculations? (Or derivations)
* Status can not be connected with a % Complete value (deprecated in #52130)
* "Rejected" children are excluded from the calcuation (#49409)
* If there is no work entered it is not possible to enter a % Complete
* The reason is: An unfinished work package (< 100 %) needs a value before Remaining work. There can not be Remaining work if there is no Work defined.
* The correct calculation is specified in <mention class="mention" data-id="40867" data-type="work_package" data-text="#40867">#40867</mention>
* Remaining work and % Complete can only be entered for a work package that has Work defined
* When creating a new work package work is 0 h \[**open:** unset?\]
* When clicking on on of the attributes (Work, Remaining work, % complete) the modal opens
* In the modal the fields Remaining work and % Complete are deactivated. The field work is active (not mandatory).
* After entering a value to Work, the Remaining work is derived.
* Example: Work 10 h, Remaining work 10 h, % Complete 0%)
* Example: Work 10 h, Remaining work 5 h, % Complete 50%)
* Deleting the field Work deletes % Complete and Remaining Work
**Current (wrong) calcuation 13.2**
<figure class="image op-uc-figure"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/88713/content"></div><figcaption class="op-uc-figure--description">https://niels.openproject-edge.com/projects/progress-calculation-1/work_packages?query_id=338</figcaption></figure>
**Correct calculation**
<figure class="image op-uc-figure"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/88712/content"></div><figcaption class="op-uc-figure--description">https://community.openproject.org/api/v3/file_links/1269/open</figcaption></figure>
###
### Open Questions
* **Migration**: If % complete will necessitate a value for Work, what happens to work package that currently only have a % conmplete without work?
* Eg pre-migration: Work = (unset), % Complete = 75%, Remaining work = (unset)
* Eg post-migrationL Work = ??, % Complete = 75%, Remaining work = ??
* **Closed status:** What happens when a work package is closed? Does % complete go to 100%?
* If so, what do we do if work was not set for that work package?
* **Work by default,** should work be 0h or unset for new work packages or work packages where "work" was not previously input?
* Note: it has to be - for the mechanism where the other two fields (% complete, remaining work) are disabled until a value for work is set.
* What does it mean (semantically) for work to be 0h?
* Does it ever really make sense for Work to be changed by the other two values?
* **Adding work:** What happens if I change the value of work?
* Example 1:
* Initial state: W = 10h, RW = 5h, % = 50%
* Action: Change W to 15h
* Three possible scenarios
* Scenario 1: W = 15h, RW = 5h (unchanged), % = 66,66%
* Scenario 2: W = 15h, RW = 10h, % = 33,33% (work done = unchanged)
* Scenario 3: W = 15h, RW = 7,5h, % = 50% (unchanged)
* Example 2:
* Initial state: W = 10h, RW = 5h, % = 50%
* Action: Change RW to 10h
* Three possible scenarios:
* Scenario 1: W = 10h (unchanged), RW = 10h, % = 0%
* Scenario 2: W = 15h, RW = 10h, % = 33,33% (work done = unchanged)
* Scenario 3: W = 20h, RW = 10h, % = 50% (unchanged)
* Example 3:
* Initial state: W = 0h, RW = 0h, % = 0%
* Action: Change W to 15h
* Result 1: W = 15h, RW = 15h (automatically set) % = 0% (automatically set)
* Is this correct?
* **Base values:** If all three values are interlinked, which of the values should other values pivot around? Which is the "main" value that should not change?
* For example, if work is increased, which one should remain unchanged?
* Remaining work
* % complete
* Work done (which is not visible)
* **Work done** = isn't this a missing field, without which users will have trouble understanding certain "automatic" calculations? (Or derivations)