Why do you need to prevent the automatic issue creation?
While preventing automatic issue creation can provide greater control, reduce noise, and ensure that only meaningful, validated Issues are logged, it also carries important trade-offs. By manually selecting which Issues to create, the organization risks bypassing the standard Issue process, and the reported control status (compliant/non-compliant) may become unreliable, reflecting only the Issues that are manually reported rather than all actual failures.
The function responsible for creating Issues automatically is _createAttestationIssue(). Disabling or bypassing this function goes against the very purpose of attestations, as it prevents the system from flagging non-compliance. In essence, the organization is no longer truly following the intended process, which undermines the reliability of control status and the integrity of the overall GRC framework.
Raf Helpful post? Don’t forget to bookmark it, give it kudos, or mark it as the answer to help the community grow!
