knobit.org

C1 (2 points)

edu:Question

https://knobit.org/id/task/dq-issue-lifecycle/C1

Also as Turtle · JSON-LD · RDF/XML

dcterms:licensehttps://creativecommons.org/licenses/by/4.0/
owl:sameAshttps://bitbucket.org/reffa/ontology/id/task/dq-issue-lifecycle/C1
rdfs:labelC1 (2 points) en
schema:hasPartdq-issue-lifecycle C1a: severity raised by the reporter re-rated from the impact (IS-103)
schema:hasPartdq-issue-lifecycle C1b: severity lowered by the reporter re-rated from the impact (IS-107)
schema:identifierC1
schema:position1
schema:textSeverity from the impact, not from the reporter, 1 each. (a) IS-103 is rated critical because the Head of Retail Sales raised it and the COO's office chased it three times; its recorded impact is a wrong branch league table in an internal weekly sales dashboard that is not in the board pack, with manual re-allocation by the regional managers - an operational impact. It becomes medium, the target date 2026-12-25, and the finding says the rating followed who raised it or how often, not the policy's impact levels. (b) IS-107 is rated low because one customer complained once; its recorded impact is interest not paid to 312 customers, EUR 18,460 already underpaid - a misstated payment to customers. It becomes critical, the target date 2026-11-08, with that impact as the reason. A severity changed without the impact as the reason earns half the part. en

Used by

has questionData quality issue register review before the stage gate - severity, ownership, duplicates, escalation and closure (issue management anomaly skills)
schema:isPartOfdq-issue-lifecycle C1a: severity raised by the reporter re-rated from the impact (IS-103)
schema:isPartOfdq-issue-lifecycle C1b: severity lowered by the reporter re-rated from the impact (IS-107)