Issue Summary

The risk item should be saved when the fields (Occurrence, Impact Value, Critical Path) are disabled in details panel settings > Risk > field list instead to generate an error message when the fields have "Not Set" value.

Finding: In JIRAALIGN-6190 note what is reported "When the fix was released for JIRAALIGN-4989, it appears that the fix is now either revealing or creating another bug of the “required field” logic on risks having a broken connection with the admin configurations on the risks' Details Panels Settings page for the Occurrence, Impact, and Critical Path fields."

Steps to Reproduce

Example using 1 of the 3 field - “Critical Path” field. The same applies to the other 2 fields Occurrence and Impact Value.

1. Portfolio_1 has Program A
2. Portfolio_1’s Risks have the “Critical Path” field toggled off in the panel settings > Risk > field list
3. Create a new Risk.
   • The Risk’s Details Panel initially displays with all fields (including the “Critical Path” field)  (and this is now behavior that I would expect to see based on the explanation here JIRAALIGN-4962 , so this is totally fine)
   • Populate the Title, Description, and Program fields on the Risk.
   • Once the Program field is populated with “Program A”, the Risk's Details Panel updates with changes to which fields are displayed since the system is now reflecting the Details Panels Settings that I’ve configured for that selected program’s parent Portfolio. So the “Critical Path” field should be hidden.
   • And this is where there does seem to be a bug now
     • The “Critical Path” field was originally showing on the Risk’s Details Panel before I selected “Program A”, and the value in that field was “Not Set” (and this “Not Set” value is displaying by default due to the change related to JIRAALIGN-4989)
     • However, once the “Critical Path” field is removed from the Risk’s Details Panel after I select “Program A,” any attempt to Save the Risk is met with an error message saying that I can’t save the Risk for as long as the “Critical Path” field’s value is “Not Set”. (Please see the image.)

Expected Results

Be able to save the item risk when the fields Occurrence/Impact/Critical in the configuration in details panel settings > Risk > field list are disabled regardless of whether fields have value "Not Set" or not. So with any values available in the list, the risk item should be saved when the fields are disabled in details panel settings > Risk > field list 

Actual Results

(Occurrence, Impact Value, Critical Path) fields disabled in details panel settings > Risk > field list and saved with  "Not Set" do not allow to save the risk item.

Workaround

Set Occurrence, Impact Value, and Critical Path fields with a value different than "Not Set"