Common custom field data should flow across Incidents, Problems & Changes

Idea created by John Crouch on Dec 28, 2016
    Under Consideration
    • John Crouch

    I can setup a custom field called "TCODE", for example, and I can add that custom field to Incident, Problem and Change.  When I set a value in TCODE on Incident, I would expect that value would be populated in Problem if I create a new Problem from that Incident, or a new Change from that Problem, for example.


    Unfortunately what happens now is even if I populate the TCODE field in Incident when I create a new Problem or Change from that Incident the TCODE field on the Problem or Change is blank and requires me to re-populate it with the same value I had in Incident.


    This is inefficient.

    What problem will this feature solve?: