Correct without erasing
Amend the plan, set a requirement aside, cancel an upload, revise an SBOM — each action justified and traced.
Evidence is only worth something if nobody could have altered it silently. QATrax therefore never modifies what it has received: each correction is an added action, with its reason, its author (the signed-in person, never a typed name) and its date. Nothing is erased; deliverables already issued keep, under their seal, what they sealed.
| you want to | where | what remains |
|---|---|---|
| correct the title, priority or description of a requirement | "Requirements" → "edit" | the history: before, after, who, when, why |
| declare a requirement not applicable | same page; justification required (CRA, Annex VII, point 3) | it leaves the calculation; the certificate lists it with its justification |
| attach a test to another requirement, change its type | "Tests" → "edit" | the history; a test that has CI results cannot become manual |
| set aside an erroneous test upload (wrong branch, wrong project) | "Runs" → "Cancel", reason required | the upload remains, marked cancelled; it is restored the same way; the next deliverable states the cancelled uploads |
| correct a manual entry | a new entry replaces it; or cancel it in "Runs" | both entries, in the test's history |
| re-import the plan or an ALM export | "Requirements" (plan, ALM) or the CI | each change made by the import enters the history, reason "plan import" or "ALM import", author (you or the CI key) |
| revise the SBOM of a version | upload it again; on screen, reason required | each different upload is a numbered revision (difference in components, author, reason); the deliverable seals the number and the fingerprint |
What cannot be done: change the status of a result received from the CI, erase a requirement, a test or an entry, alter an issued deliverable. An error is corrected by a new, visible action — this is what makes the evidence enforceable.