Previous Topic

Book Contents

Book Index

Next Topic

Add a new Ticket Description

Use case scenario: If you want to add new information (e.g. additional information requested from the end user) to the ticket, you need to create a new ticket description. Ticket descriptions can also be used for registering the details and steps of Incident diagnosis.

Note: The Ticket description may also serve as an escalation tool regarding the processing of an Incident. A user experiencing delays or a failure to restore his services can open his Incident and add a ticket description with a complaint anytime. Please see also the 'Track Own Incident Tickets' topic.

The following actions are involved in the process:

Create

This is the Create button in the Descriptions section of the Incident editor. It allows you to create a new ticket description.

General Visibility

A check box which enables you to make the description visible to the end user.

 

To add a new ticket description:

  1. Click the Create button in the Descriptions section of the Incident editor.
  2. Select a Statement Type (the standard is 'Comment').
  3. Fill in a Ticket Shorttext and a Description.
  4. Optionally, you can use the Checklist-Entry field to add some structured information to the description.

    See 'Checklists in Ticket Descriptions' below for more information.

  5. Check the General Visibility check box to make the description visible to the end user.
  6. Click OK to proceed.

Note: If individual steps of Incident processing (e.g. contributions to Incident diagnosis) should be handled in a predefined sequence by various support groups, ticket Activities will be used instead of Descriptions.

Checklists in Ticket Descriptions

A ticket description can be optionally supplemented with additional information structured in the form of a checklist questionnaire. This is done by attaching an object of the 'Questionary' object type to the ticket description.

To add a supplementary checklist to a ticket description:

  1. Locate the Checklist-Entry reference view on the Master tab of the ticket description editor.
  2. Click the Add new button in the reference view. A browser of available questionnaire types opens.
  3. Select one of the predefined questionnaire types.

    Examples include 'General Interruption', 'Network not available' or 'Phone Change Requirement'.

  4. Click OK in the browser to confirm your selection.

    A new questionnaire of the selected type opens in its own editor.

  5. Fill in relevant fields and click OK to proceed.

    The questionnaire editor closes and the newly created object is linked to the ticket description.

    It can be re-opened for editing by clicking the 'Edit' button in the 'Checklist-Entry' reference view.

The attached checklist questionnaires are primarily intended for use with ticket descriptions of 'Checklist' statement type. While their use with ticket descriptions of other statement types is also possible, for 'Checklist' statement type attaching a questionnaire is mandatory.

Customization information: Each checklist questionnaire (or, more precisely, each questionnaire type) is represented by a separate view defined for the 'Questionary' object type. A new, customer-specific checklist questionnaire can thus be added by creating a new view for the object type and providing attribute translations corresponding to the type of data the questionnaire asks for.

The two images below provide an example of the predefined 'General Interruption' questionnaire type - the actual editor and its preparation in the view customizer.

Help Image
General Interruption: The questionnaire editor

Help Image
General Interruption: The view customization

See Also

Work on Incident

Create Incident

Accept Incident and check responsibility

Assign Incident

Search solution in KB

KB Proposal

Solve Incident

Inform end user about the Incident Solution

Close Incident

Feedback: Incident solution not accepted

Postpone Incident

Assign Incidents to a Problem

Check Present Status of an Own Incident

Incident Priority Change Reason

Relate 'N' Systems or Components to an Incident/Problem

Incident Reporting

Incident - RFC/Change