Updated on 2025-08-08 GMT+08:00

Creating a Change Ticket

Scenarios

If an application requires changes, you can create a change ticket to record the change scope and solution. You can upload a detailed change solution or implement the change by executing jobs.

Prerequisites

  1. You have created an application by referring to Application Management.
  2. You have created a reviewer shift schedule by referring to Overview.

Precautions

Confirm the content of change ticket and apply for the change based on the actual change requirement.

Creating a Change Ticket

  1. Log in to COC.
  2. In the navigation pane on the left, choose Change Ticket Management > Change Center.
  3. Click Create Change Ticket in the upper right corner.
  4. Configure the basic information.

    • Title: Customize the title of the change ticket.
    • Description: Describe the change. Enter a maximum of 4,096 characters.

  5. Set Change Configuration.

    Table 1 Changing configuration parameters

    Parameter

    Description

    Example Value

    Change Type

    The options are Regular and Urgent.

    • Regular changes are non-emergency changes that can be requested, evaluated, reviewed, sorted, planned, tested, and implemented using regular procedures.
    • Emergent changes are unplanned changes that are proposed because the production environment is unavailable or the changes cannot be evaluated and approved in time through the normal process, or to meet urgent service requirements.

    Regular

    Level

    The options are A, B, C, and D (A > B > C > D).

    A

    Scenario

    Select a change scenario from the drop-down list.

    API change

    Application

    Select a change application, a sub-application, a group, and a component from the drop-down lists as required. Multiple sub-applications, groups, and components can be selected.

    N/A

    Region

    Select a region from the drop-down list. Multiple options can be selected.

    CN-Hong Kong

    Selected Change Scope

    Configure the change region corresponding to the sub-application, group, and component.

    N/A

  6. Configure Change Plan.

    Set the change plan for the selected regions.

    Table 2 Change plan parameters

    Parameter

    Description

    Planned Change Time

    Select a time range for the plan change.

    Change Implementer

    Select a change implementation user. Multiple users can be selected.

    Change Coordinator

    (Optional) Select a user as the change cooperation. Multiple users can be selected.

  7. Configure information in Task Type.

    • Task Type: Select Jobs or Change guidelines.
    • If Task Type is set to Jobs, configure other parameters by referring to Table 3.
      Table 3 Job parameters

      Parameter

      Description

      Task Type

      Select the job you want to execute from the drop-down list.

      Region

      Select a region from the drop-down list.

      Target Instance Mode

      This parameter is only required for some jobs. You can select the execution methods for job steps and target instances.

      • Consistent for all steps: All tasks are executed on the selected instance using the same batch policy.
      • Unique for each step: Tasks in one step are executed on the selected instance. Each step uses a batch policy.

      Job Execution Procedure

      This parameter is required for some jobs. You can customize job details.

      • Click a job name. The drawer for modifying parameters is displayed on the right.
      • Set Input, Output, and Troubleshooting.

      Global Parameters

      This parameter is required for some jobs. You can set global parameters.

      Target Instance

      This parameter is required for some jobs. Click Add Instance and set Select Instance.

      For details about how to set the parameters, see Table 4.

      Batch Policy

      This parameter is required for some jobs. You can select Automatic, Manual, or No Batch.
      • Automatic: The selected instances you want to execute are automatically divided into multiple batches based on the preset rule.
      • Manual: You can manually create multiple batches and add instances to each batch as required.
      • No Batch: All instances to be executed are in the same batch.
      Table 4 Parameters for selecting an instance

      Parameter

      Description

      Example Value

      Selection Method

      Select an instance selection method.

      • Manual Selection: Manually select an instance based on Enterprise Project, View Type, Resource Type, Region, and Target Instance.

      Manual Selection

      Enterprise Project

      Select an enterprise project from the drop-down list. You can choose All.

      All

      View Type

      Select a view type.

      • CloudCMDB resources: Select an instance from the resource list.
      • CloudCMDB application groups: Select an instance from the application group list.

      CloudCMDB resources

      Resource Type

      The value can be ECS or BMS.

      ECS

      Region

      Select a region from the drop-down list.

      CN-Hong Kong

      Target Instance

      Set filter criteria in the filter box and select the filtered instances.

      N/A

    • If Task Type is set to Change guidelines, see Table 5 to set required parameters.
      Table 5 Parameter description for the change task that is based on change guidelines

      Parameter

      Description

      Task Type

      Click Add File to upload the files related to the change guidelines.

      A maximum of 10 files can be uploaded. The supported file types are JPG, PNG, DOCX, TXT, and PDF. The size of a single file cannot exceed 10 MB.

  8. Click Submit.
  9. Click OK.

    The change ticket is created. Choose Change Ticket Management > Change Center. Switch to the Created by Me tab page to view the created change ticket.