Create change request forms

  • リリースバージョン: Australia
  • 更新日 2026年03月12日
  • 所要時間：4分

    • Fill out the fields in the forms to create a change task to implement a controlled process for modifying approved and supported actions for SRM.

    Change request form

    Create a new change request. For more information, see Manually create an SRM change task.
    Field Description
    Short description Brief description of the change request.
    Description Description based on Short description.
    Number Identifier for the change request.
    Category Category for the change request.
    Choices are:
    • Hardware
    • Software
    • Service
    • System Software
    • Application Software
    • Network
    • Telecom
    • Documentation
    • Other (default)
    Model Model to use for the change request.

    Standard (default)
    Risk Risk the issue poses.
    Choice are:
    • High
    • Moderate (default)
    • Low
    Type Type of change request.

    Standard (default).

    Read-only.
    Impact Impact the issue poses.
    Choices are:
    • 1 - High
    • 2 - Medium
    • 3 - Low (default)
    State State of the change request.
    Choices are:
    • New (default)
    • Assess

      If approval is required further states are unavailable.

    • Scheduled
    • Implement
    • Canceled
    Work notes list Team members to receive notifications when work notes are added.
    注:
    An administrator must have already created an email notification for the work notes list for this to be available.
    Work notes Any additional information related to the request.

    Impact, Assignment, Planning, Schedule, Notes, and Closure information

    Field Description
    Configuration item Asset affected by the issue.
    Service Service affected by the issue.
    Service offering Service offering affected by the issue.
    Assignment group Team assigned to the change request
    Assigned to User assigned to the change request.
    Justification Reasoning for the change request.
    Implementation plan Imported text.
    Risk and impact analysis Analysis of risk and impact of the issue.
    Backout plan Imported text.
    Test plan Imported text.
    Planned start date Expected date to begin change.
    Planned end date Expected date to finish change.
    Actual start date Date change implementation began.
    Actual end date Date change implementation ended.
    Conflict status Not run. Read-only.
    Conflict last run Based on Conflict status. Read-only
    Watch list Interested users.
    Work notes list Team members to receive notifications when work notes are added.
    注:
    An administrator must have already created an email notification for the work notes list for this to be available.
    Additional comments Additional notes for the request.
    Work notes Additional notes on the work done for the request
    Close code Code for the change request.
    Choices are:
    • None (default)
    • Successful
    • Successful with issues
    • Unsuccessful
    Close notes Notes on the change request closure.