IPT, labeled as "Issue created from Group by Control Owner"

driver
Kilo Contributor

Has anyone dealt with automatically-generated audit issues (IPT, labeled as "Issue created from Group by Control Owner")?  If the issues is manually generated, is this not redundant?  Thanks!

1 ACCEPTED SOLUTION

Phil Swann
Tera Guru
Tera Guru

There is a business rule on sn_grc_issue called: Auto group issue based on rule

 

If the Item is not empty and the Parent is empty, AND the Item's content has an Issue Group Rule defined...

e.g. the Control's Policy Statement (Control Objective) or the Risk's Risk Statement

 

 

It gets or creates a group issue: new sn_grc.IssueGrouping().groupIssueBasedOnRule(current); 

And sets that as the Parent...

 

so to your question, does it matter if the issue is manually generated? No.

It matters if you set an item, do not set a parent, and that the item's content has an Issue Group Rule defined! 

 

View solution in original post

4 REPLIES 4

Community Alums
Not applicable

Is this issue still valid?

Phil Swann
Tera Guru
Tera Guru

There is a business rule on sn_grc_issue called: Auto group issue based on rule

 

If the Item is not empty and the Parent is empty, AND the Item's content has an Issue Group Rule defined...

e.g. the Control's Policy Statement (Control Objective) or the Risk's Risk Statement

 

 

It gets or creates a group issue: new sn_grc.IssueGrouping().groupIssueBasedOnRule(current); 

And sets that as the Parent...

 

so to your question, does it matter if the issue is manually generated? No.

It matters if you set an item, do not set a parent, and that the item's content has an Issue Group Rule defined! 

 

Stefano12
Kilo Explorer

Hi,

as far as you know, can the parent issue (the one automatically generated) be deleted without impacts on the children (the ones manually created)?

Thanks in advance!

this is a different question to the one posed, but yes. 

However, check in sub-prod first - and suggest decoupling first if possible. 

 

If you can validate on the dictionary entry there is no cascade delete rule on the sn_grc_issue.parent_issue field this should confirm... but do not just take my word for it and delete directly in Prod without prior validation 🙂 good luck