Resolution Code differentiated by Ticket Type

Idea created by rioad01 Employee on Sep 17, 2015
    Not planned

    Process incident is differente that process request, therefore, the Resolution Code is valid by Incident, but not by Request. This name should apply to the two in the label should be consistent with each process, for example: by incidents resolution code, by request reason code. My idea is that this table can have other option by mark if the value is by Incident o Request, as a check box, and accordingly it is shown in the form of incidents and requests, similar to the behavior of the field AREA (prob_ctg). Also allow viewing not in list, but rather in scheme by level, differentiated by points, as do the areas AREA (prob_ctg).  This would also apply to Root Cause, distinguishing whether it is for problems or changes.