Done
Details
Assignee
Andrei MakarankaAndrei MakarankaReporter
DamienDamienPriority
P2Story Points
1Sprint
NoneDevelopment Team
ThunderjetFix versions
TestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Andrei Makaranka
Andrei MakarankaReporter
Damien
DamienPriority
Story Points
1
Sprint
None
Development Team
Thunderjet
Fix versions
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created May 17, 2021 at 3:39 PM
Updated June 7, 2021 at 8:15 AM
Resolved June 7, 2021 at 8:15 AM
Purpose/Overview:
MODFISTO-233 added a test to prevent unreleasing encumbrance if it was expended (the implementation was simply checking if amountExpended is different from 0). This is causing an issue when reopening an order: in some cases, we want to unrelease expended encumbrance.
Requirements/Scope:
Requirement It should be possible to reopen an order with expended encumbrance
Approach:
A possible fix is to revert the check added in MODFISTO-233 and allow to unrelease expended encumbrance. Additionally, the new amount for an unreleased encumbrance should be changed to initialAmountEncumbered - amountAwaitingPayment - amountExpended.
Acceptance criteria:
Updated modfisto implementation, updated unit tests (see code and test added for MODFISTO-233).
Integration tests should replicate use cases given in the comments.