Problem Management - Cause Codes ONLY in PTASKs?

[MC_Teknaut]

SN Experts,

I've noticed a highly beneficial field within Problem Tasks (PTASK) - "The Cause Code". These codes provide very contextually valuable information. My issue is that it's currently nested within PTASKs only. Is it possible to place this field within the parent PRB ticket? Not every problem ticket will need a PTASK opened and it would be great to be able to show that an Environmental Disaster or 3rd Party issue is at hand. I feel like I cancel a lot of Problem tickets because there wasn't a great way to capture it not being a "valid problem management candidate". 

The field is otherwise seen nowhere else, and people in my organization aren't really aware of this valuable field. Surely there's a more "front and center" way to use this?

I've asked another question on the use case of Cause Codes vs. Cancelling PRBs - Forum Link Here

[Harish KM · Accepted solution]

Cause Code is a field created on Problem Task table , so you cannot display on Parent (problem) table. You can create a another choice field on Problem table and match the values from child to parent through script.

or you could use cause notes field on Problem table to insert the value when problem task is closed through script. This would avoid new custom field creation.

[MC_Teknaut]

Harish,

Thank you for the answer! 

However, I have provided my feedback via the feedback community because I believe that Cause Codes (when sequestered away in PTASKs) are currently a wasted metric. Why would I need to open a Root Cause Analysis PTASK when I know that an issue was created by an Environmental Disaster? I've already cancelled the PRB ticket at this point, because you can't Manage Problems that are created by nature.