The Project Risk, Issue and Change Summary report query joins the SRM_RESOURCES table at the wrong field. It is pulling from the ID field opposed to the USER_ID field for the 'Assigned To' column. This causes the resources names showing on the 'Owner' column on the report to be inaccurate.
Steps to Reproduce:
- Create a Project
- On that project, create a 'Risk A' on the Risk/Issues/Changes tab
- For the 'Owner' field, select Resource1
- Save the Risk, and run the 'Project Risk Issue and Change Summary' report
Expected Result: 'Risk A' shows Resource1 on the 'Owner' column
Actual Result: 'Risk A' shows a different Resource on the 'Owner' Column
Copy the existing report, and create a brand new report with this slight change in the code:
On the Project Risk Issue and Change Summary report query, look for this line:
LEFT OUTER JOIN srm_resources own ON r.assigned_to = own.id
It needs to be changed to this:
LEFT OUTER JOIN srm_resources own ON r.assigned_to = own.user_id
This also affects the Project Risk Register and Project Issue Register reports in Clarity 13.3. The same workaround applies to these two reports using their corresponding queries.
This issue is documented as CSP-158 and affects CSP 3.3
Resolved in Clarity 14.1 Solution Pack (CSP)