CAST Engineering Dashboard - Violations - Wrong involved objects in path - List of involved objects in Path is empty for QR Avoid Too Many Copy Pasted Artifacts

 In the quality model drill down, the list of involved objects in Path is empty for QR: Avoid Too Many Copy Pasted Artifacts.

When you are expecting to see the list of objects containing copy-pasted source code

1. Generate a snapshot on an application.
2. Connect to the quality model drill down.
3. Go to quality rule "Avoid Too Many Copy Pasted Artifacts" underTechnical Creteria "Architecture-Reuse" underBusiness Criteria "Total Quality index".
4. Go to the bottom right to see the "Involved Objects: The list of "Involved Objects" is empty.

The impact of the problem on the analysis or the dashboard is: The list of "Involved Objects" is empty.

Issue can be due to an inconsistency between the data in the KB and in the CB for the group_ids attributed to group of objects considered as copy pasted.

As a consequence, in the dashboard it is not possible to find the list of involved objects in Path and show it as empty.

To check if you are facing this inconsistency,

1. Run the following query by replacing the <CentralDB>, <localDB>, and <last_snapshot_id> with the right values.

   select distinct METRIC_NUM_VALUE
   from <CentralDB>.DSS_METRIC_results a
    where a.METRIC_ID = 7157 --metric Avoid Too Many Copy Pasted Artifacts
    and a.SNAPSHOT_ID = <last_snapshot_id>
   and a.METRIC_NUM_VALUE not in (select GroupId from <localDB>.DSS_CodeGroup)

   If this query returns some rows, you have an inconsistency between the data in the KB and in the CB for the group_ids attributed to group of objects considered as copy pasted.
   

2. To fix this corruption, rerun the snapshot by skipping the analysis.
   
   
   
3. If you are still facing the issue after running the snapshot, contact CAST support,with the Sherlock output and screenshot of the issue.

Impact of the solution on the analysis or the dashboard is: The list of "Involved Objects" is correctly computed.

 Ticket # 4517

Since the only issue encountered up to now is a corruption on the DBs that is no longer reproducible after rerunning snapshot, no correction has been done on the product.