Creating a Change Request

change requests are divided into five different types each type of change request defines the priority of the change in relation to other changes, the speed at which the change must be implemented, the size of the impact that the change makes on the organization do one of the following log in to the console and open the change workspace within a form (such as incident, problem, or release), select the change tab from the toolbar, click new change to open a blank form, or select a template from the drop down list a change form is displayed if you used a template, some data already appears in the fields if you create a change request as a or another user who does not have permissions, only a subset of fields on the change form is displayed results may vary depending on your application setup details see step 3 working with tasks docid\ e40f2roctrskvptf1awpc creating a service docid 2bvrzyy 8f2vwf83sofug risk level docid\ tne5dflsi1ffxjaje4pfl change schedule docid\ ithbzn cxavpffdg7gjkz attachment docid\ dwyg6strtal1zdoaecfjz about activity history docid\ dolnqxplsr ccl3 udx4k about creating a configuration item docid\ zmfn pxt6cjewpqpaj6wp managing incidents docid\ akruodyqj2wvb c6ayolg working with problems docid\ set5um 9o nw5unsjvtf announcement docid\ hy7mtijubhswom5fapc4k working with workflow instances docid\ uyae8z1xcnbsxjkmao7e9 audit history docid\ suej5xmlyduoz68lbfgae baseline docid\ emdkl6p3bsrodtmy2kqrc about the related posts tab docid\ btgspwcozfq6p1aq2wqu5 approval docid\ rr3pjabsqaohrubv2scko the approval tab is displayed only if an approval is needed for a task on the change request under the details tab, enter information into the fields field description requested by the person requesting the change the application automatically enters the name of the logged in user, but you can change this if you are not the requester of the change sponsor the name of the sponsor of this change team the team associated with the person requesting the change coordinator the coordinator requesting the change defined from the team list cab vote expiration the deadline date and time for the change approval board (cab) to vote to approve or deny this change the date and time must be after now cab review date the deadline date and time for the cab to review this change the date and time must be after now approved by/on this field is automatically populated by the application, based on the approval workflow cost this field is automatically populated by the application time the time spent is based on the activity history, is automatically generated by the application, and is given in minutes summary subject or title of the change description details of the change status the status of the change only s can modify a change status see change business object reference docid\ w8if3surpl0wr0popjkhw for details on each change status type the type of change standard this type of change is performed on a regular basis and is considered routine standard changes are typically created through one of the various change templates available a user cannot create a standard change in the same fashion as other changes emergency this type of change is usually a response to a failure or error that needs an urgent fix emergency changes must be made quickly and is usually recorded after the change has already been made major this type of change requires a lot of items or dependencies and may require other associated change requests minor small changes or changes that have a small or minor affect are classified this way significant similar to major except that significant changes might need to be divided into several partial subsequent changes that together would constitute a large significant change, depending on the policies and requirements of your organization category the category of the change justification the reason for the change risk level automatically shows the results of the risk level tab urgency the time appropriateness required the default value is 3 urgency and impact together define the priority value high necessary immediately with a high degree of urgency medium required, but can be made after higher urgency changes have been implemented low required, but can wait for other changes of greater urgency to be implemented impact impact to the organization, group, or individual the default value is 3 impact and urgency together define the priority value high has a major impact on the organization medium has some effect on the organization but generally not considered a large effect low does not have much effect on the organization backout plan attached specifies that there is a backout plan to the record under the attachment tab attach the required supporting documents before setting the change to pending review status changes tested specifies if you have tested the changes described in this record start date the date and time when the event starts end date the date and time when the event finishes release the related release number the release must be defined in the release workspace click save the change request remains in the logged state while you are working on the change request record