C2 (3 points)
https://knobit.org/id/task/dg-issue-escalation-closure/C2
Also as Turtle · JSON-LD · RDF/XML
| dcterms:license | https://creativecommons.org/licenses/by/4.0/ |
|---|---|
| owl:sameAs | https://bitbucket.org/reffa/ontology/id/task/dg-issue-escalation-closure/C2 |
| rdfs:label | C2 (3 points) en |
| schema:hasPart | dg-issue-escalation-closure C2: GI-044 decision not written back to BT-106 |
| schema:hasPart | dg-issue-escalation-closure C2: GI-045 decision not written back to ST-011 |
| schema:hasPart | dg-issue-escalation-closure C2: GI-044 not closed before write-back |
| schema:identifier | C2 |
| schema:position | 2 |
| schema:text | Decisions not written back to the deliverable they change, 1 each. (a) GI-044's decision (available balance = ledger balance less holds and less uncleared cheque deposits) changes glossary term BT-106, which still reads 'the ledger balance less holds' and cites no issue: reported (decision-not-written-back, or an equivalent finding naming GI-044 and BT-106) and a change request asks RO-002 to update BT-106 with GI-044 in its source_issues. (b) GI-045's decision (98 % for secured loans originated before 2012) changes the threshold in standard ST-011, which still says 100 % and cites no issue: reported and a change request raised for ST-011 citing GI-045. (c) GI-044 does not stay closed: it goes back to decided (or open) with next_step write_back, because an issue is closed only after its decision is written back and verified - the check of the app alone does not close it. en |