'Create Issue from Risk' system action results in an error if there are mandatory attributes in the Risk and Issue objects

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

An issue with 'Create Issue from Risk' action has been identified. Steps to reproduce it are as follows.

1. Navigate to Administration -> Processes. Create a new process
2. Add Risk as a linked object under the process
3. Connect the start step to the finish step
4. Create a new system action in the Start Step:
   
   1. Set "Action" = "Create Issue from Risk"
5. Validate and Activate the process
6. Navigate to Administration -> Objects
7. Search for "Risk" object and create a new attribute within it:
   
   1. Mark the attribute as value required
   2. Note down the attribute ID
8. Search for "Issue" object and create a new attribute within it:
   
   1. Mark the attribute as value required
   2. Provide the same attribute ID as in Step 7
9. Navigate to a Project in the Classic UI -> Risk/Issues/Changes tab
10. Create a new Risk. Populate the mandatory field from Step 7
11. Navigate to Proceses -> Available. Trigger the process from Step 5

Expected Results: An Issue is created from the Risk instance.

Actual Results: The process throwns an error: "Could not create the issue instance".

The following error message is thrown in the bg-ca.log:

"
ERROR 2022-01-14 03:00:42,939 [Action Execution Pipeline 0 (tenant=clarity)] utilities.BpmErrors (clarity:process_admin:5752041__E045DF5F-3CA9-44AC-BC55-E3FB181A7818:none) BpmErrors::getExceptionTrace(String arg) => 
com.niku.union.odf.exception.ODFValidationException: Could not create the issue instance.
 at com.niku.odf.object.Utils.execService(Utils.java:226)
 at com.niku.odf.object.Utils.execService(Utils.java:284)
"

Environment

Version: 16.0.0.

Cause

This behaviour was reviewed by Product Management via DE63776.

Resolution

The defect that was raised was closed, since Product Management determined that changes to this behaviour would have to be routed through an enhancement request.

Following is an excerpt from the explanation provided by Product Management:

1. At the moment, no such logic/behavior exists to take the matching attributes from source instance and setting to target instance in the system action mentioned above (and there are 5 other system actions in RICs.. same is the case with these too). This is how it's been working starting from the original implementation
2. The defect tries to compare this with idea to project conversion functionality, however, the way idea to project conversion works today is via ‘CopyEngine’ with the help of mapping infrastructure, etc., whereas all these 6 system actions in RICs are plain and do not have this sort of logic implemented.