Failed Indicator Task Generates Two Issues

leport
Tera Contributor

‎10-30-2025 07:47 AM

Not sure I am in the right place. We are testing the Zurich upgrade prior to adoption and we have noticed "a new feature" within the Compliance modules.

 

When an Indicator Task is closed as FAIL, the system is generating two Issues:  One is associated with the Control Objective / Risk Statement (See attached screenshot named Parent Issue) and the other is also associated with the Control Objective / Risk Statement but it is also linked to the Entity  and Control Risk that was associated with the Indicator Task (see attached screenshot named Child). And the two issues are linked in a parent-child relationship


This is not something happening in our Xanadu instances.  In Xanadu, one issue is generated and linked to the Control Objective / Risk Statement, Entity and Control/Risk records. (See attached screenshot named Xanadu)

 

We are trying to understand these are being separated the Zurich Release.  What is the use case/purpose for second issue that is linked the the Control/Objective / Risk Statement only?

Preview file
50 KB
Preview file
50 KB
Preview file
58 KB
0 Helpfuls
  • 319 Views
1 REPLY 1

Matthew_13
Tera Guru

yesterday

Hi,

What you’re seeing is indeed a change in behavior in Zurich compared to Xanadu. In Zurich, the system creates two issues for a failed Indicator Task:

  1. Parent Issue – linked only to the Control Objective / Risk Statement.

  2. Child Issue – linked to the Control Objective / Risk Statement and the specific Entity and Control/Risk from the Indicator Task.

Purpose / Use Case

  • Parent Issue serves as a high-level summary for the Control Objective / Risk Statement. It tracks overall compliance failure at a broader level.

  • Child Issue captures the specific instance tied to the Entity and Control/Risk. This allows detailed tracking, remediation, and reporting on specific areas without cluttering the summary.

Basically, Zurich separates summary vs. detailed issues to provide better visibility and traceability:

  • Parent = overview for the compliance team.

  • Child = actionable tasks tied to specific entities and controls.

This is intentional and part of Zurich’s compliance module enhancement for more granular tracking.

If needed, I can explain how to adjust workflows or reporting to make these two issues easier to manage. Let me know.

@leport 

PLEASE MARK AS SOLUTION ACCEPTED AND THUMBS UP IF YOU FIND HELPFUL. THANKS KINDLY

0 Helpfuls