I have a client that has started using Risks and have found an issue with the tool. I was wondering if anyone else has experienced this and what workarounds you may have implemented. Here is a summary of the issue.
When you create a risk with a Category that aligns with the OOTB risk categories, the project level risk attribute is set to match the Calculated Risk of the risk entered on the project. So if you create a risk with a category of "Flexibility" with a calculated risk of "High", the Flexibility Risk attribute on the project is set to "High". This is as designed. The issue occurs when you resolve the issue, the OOTB Project level attribute gets set to NULL, which invalidates the Overall Risk calculation on the project.
I would expect that either the Flexibility risk would be set to Low, OR that the Overall Risk calculation would account for NULL values.
Has anyone else seen this and implemented a workaround?