Change fields and their behaviour

field label field type field behaviour purpose actual end date and time mandatory when of status "post implementation review" or "completed" on wards this is the date and time that the change implementation actually ended actual start date and time mandatory when of status "post implementation review" or "completed" on wards this is the date and time that the change implementation actually started approvals multiple reference (workflow task table) shows the approvals that have taken place for a change, as well as who is being requested for approval approver multiple reference (user table) visible and mandatory when change is being requested for peer review for change types of "minor" and "major" determines who gets asked for approval (in addition to the other approvers that are automated) when a minor or major change gets submitted for approval assignee reference (user table) mandatory when change is being completed user must be a part of the assignment group, be active and have the itsm agent role or administrator role is automatically cleared if the assignment group changes and they are not a member of the group this is the individual responsible for the completion of the change assignment group reference (group table) mandatory group must be selectable, have change listed in the accessible from table field or the accessible from table field must be empty this is the group that is responsible for the completion of the change attached knowledge reference (knowledge table) read only automatically set when knowledge is attached from sofi this is used to understand what knowledge was used for a change business justification string mandatory when change is being requested for peer review this is the business justification as to why a change should be implemented change type choice values emergency minor major pre approved unscheduled emergency mandatory these are the change types that a change can follow depending on the change type, will depend on the different mandatory fields, approval steps and general workflow of a change classification reference (classification table) mandatory must be selectable and for the change table this is the classification that can be selected from a change that can help for reporting or otherwise closed at date and time read only automatically set this is automatically set based on the date and time that the change s closed closed by date and time read only automatically set this is automatically set based on the person that closes the change collaborator multiple reference (user table) users must be active and have the itsm agent role or administrator role these are any users who may be assisting in the completion of the change or want / need to be kept up to date as to the progress of the change this is also used to assist with the "changes i'm following" menu item completed at date and time read only automatically set this is automatically set based on the date and time that the change is completed completed by date and time read only automatically set this is automatically set based on the person that completes the change completion notes string mandatory when change is being completed used to provide information as to how a change was completed description string extra information that can be provided as part of the change impact choice values critical high medium low mandatory when change is being requested for peer review this holds the potential impact of the change if it was to go wrong implementation plan html mandatory when change is being requested for peer review, unless it is of change type "unscheduled emergency" mandatory when it is in the status of "post implementation review" when change is of type "unscheduled emergency" this is the step by step plan that a user can outline the steps that will be taken when the change is being implemented planned end date and time mandatory when change is being requested for peer review this is the date and time that the change implementation is planned to end planned start date and time mandatory when change is being requested for peer review this is the date and time that the change implementation is planned to start post implementation review html mandatory and visible when status is of type "post implementation review" and change is of type "major", "emergency" or "unscheduled emergency" the details as to how successful or unsuccessful a change was implemented, to be able to take continual learnings from it priority choice values p1 | critical p2 | high p3 | medium p4 | low p5 | planning mandatory the priority of a change used for reporting purposes, conditional logic purposes and sla purposes reference number auto sequence (prefix is chg) read only automatically set display value used as a unique reference to a change and its display value related configuration items multiple reference (cmdb table) used to highlight any configuration items related to a change related incidents multiple reference (incident table) these are the incidents that are related to a change that will be automatically resolved once the change has completed related problems multiple reference (problem table) these are the problem that are related to a change that will be automatically resolved once the change has completed related requests multiple reference (itsm request table) these are the itsm requests that are related to a change that will be automatically completed once the change has completed remediation plan html mandatory when change is being requested for peer review, unless it is of change type "unscheduled emergency" mandatory when it is in the status of "post implementation review" when change is of type "unscheduled emergency" this is the step by step plan that a user can outline the steps that will be taken if the change goes wrong and either needs to be backed out, or fixed forward requested by date date and time mandatory when change is being requested for peer review this is the date that the change is requested to have been implemented by reviewer multiple reference (user table) mandatory upon asking the change for review these are the users who review a change, prior to asking for approval, to determine if the change is in the correct change type and should be implemented risk choice values critical high medium low mandatory when change is being requested for peer review this is the risk that the change may go wrong and / or the risk to the greater organisation service reference (service table) this is the service that can be selected from a change that can help for reporting or otherwise short description string mandatory the short description is used as the primary classifier source for sofi sofi conversation id string not visible on the form used to hold the sofi conversation id, which is used by the sofi continuation point dialog manager element subtasks multiple reference (change task table) these are the change tasks that have been created from and are related to a change test plan html mandatory when change is being requested for peer review, unless it is of change type "unscheduled emergency" mandatory when it is in the status of "post implementation review" when change is of type "unscheduled emergency" this is the step by step plan that a user can outline the steps to test the change once it has been implemented, to determine it was implemented successfully work journal journal this is the method to communicate internally about a change other fields hidden from form and un used the below are fields that come off one of the tables changes extend from, which it does not use or have on the form some will have some behaviours tied to them (due to existing on the work table), but some will have nothing tied to it as a result, you can use them, but they will likely have no functionality tied to them note that there are other fields, but they are not recommended to be used due to the potential impact field label field type field behaviour purpose client journal journal as clients are recommended not to view changes, this field is not visible on the form and is not used follower multiple reference (user table) as clients are recommended not to view changes, this field is not visible on the form and is not used parent reference (work table) read only not used for any purpose at the moment, but can be used in the future requested for reference (user table) mandatory as clients are recommended not to view changes, this field is not visible on the form and is not used requestor reference (user table) mandatory as clients are recommended not to view changes, this field is not visible on the form and is not used