Generating issues automatically or keep it manual

[Noor_Mtl]

We are in the design of IRM. I know that issues can be generated automatically when a control or a risk indicator fails. I am hesitant to turn the automation on because a lot of issues are going to be reported manually and I am concerned with duplication.

Any input on whether it is better to go with automatic creation of issues or not in the first phase of IRM deployment?

[Community Alums]

Hi @Noor_Mtl ,

Automatic and manual both should be Ideally present and you can find out if the issue was created automatically or manually by "Issue Source" in the sn_grc_issue" table. Like Below:

Moreover, automatic issue creation is OOTB, no additional effort required.

[Connor Levien]

@Noor_Mtl it is strongly suggested to keep the automated issue creation when a control or risk indicator as this helps you get the most out of the product. Additionally, there are smarts built into the issue creation process so it wont create duplicates. For example you have a control indicator that runs each day and has failed on consecutive dates, it wont create a new issue each day it will instead append the indicator result each day to the existing open issue. This also includes if there is a manually raised issue and an indicator fails it will add to the existing issue rather than duplicating.

Furthermore you can also use issue grouping rules to bundle together manual issues using your own logic.