Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Merged branch "DOC0001399" into parent


Tip

Role required: incident_manager.

Create an incident announcement

You can create an announcement to inform affected users that the incident is being processed.

To create an incident announcement, complete the following steps: 

  1. Navigate to Incident Management → All Incidents and open the incident you need.
  2. Click the Create Announcement in the top right corner of the form.
  3. Fill in the fields. 
  4. Click Save or Save and Exit.

You can create as many incident announcements as you need. 

As a result, a new announcement is created in the Announcement table. It has a reference to the incident in the Related Incident field. This announcement record is also displayed in the Related Lists area on the incident form.

Incident Announcement form fields

FieldMandatoryDescription

Number 

YThis field contains an announcement number in ANCMXXXXXXX format and is populated automatically.StateY

Announcement state. This field is populated automatically with New when the announcement has just been created. Other options:

  • Review – the announcement must be reviewed. After setting this state, notifications are sent to all emails specified in the Reviewer’s Email field.
  • Published – the announcement is displayed on the Self-Service Portal and/or sent via email. Select the via Email and/or via Portal checkboxes, accordingly. 
  • Inactive – the announcement is inactive. It is not displayed on the Self-Service Portal and not sent via email.
Tip

Only active announcements {state IS Published^via Portal IS Yes} are displayed to the Portal users.

For more information, see General Concepts and Procedures

Related IncidentYThis field is populated automatically with the number of the incident.Announcement Type Y

Available options:

Recovery– informs that some services or CI recovery activities have been started.
  • Completion Recovery – informs that some services or CI recovery activities are over.
  • ServiceYSpecify the service affected by the incident.Recipient EmailNSpecify the email of the announcement recipient. You can add more than one email, separated by commas.Reviewer's EmailNSpecify the email of the announcement reviewer. You can add more than one email, separated by commas.SubjectYThis field is populated automatically with the subject of the incident.Announcement BodyNType a message about the incident to share with the affected users. You can design the announcement body using the built-in editor functionality, such as by formatting the text, working with tables and media, lists, styles, and headings.SignatureNReference to the Announcement Signature.DescriptionN

    Add a description for the announcement.

    via EmailNSelect the checkbox to send this announcement via email. It will be sent to all addresses specified in the Recipient Email field.via PortalNSelect the checkbox to display this announcement on the Self-Service Portal in the Portal Announcements area.

    Create relationships

    You can create relationships between incidents and other types of tasks.

    To create a relationship, complete the following steps:

    1. Navigate to Incident Management → All Incidents and open the incident you need.
    2. Open the Related Records tab.
    3. Click the magnifier icon next to the appropriate field.
    4. In the window that appears, choose the necessary option.

    5. Сlick Save to apply the changes.

    Relationship types

    TypeDescription
    Related ProblemsThe incident is related to the problems specified.
    Related User QueryThe incident is related to the user query specified.
    Solved by ChangesThe incident is solved or can be solved by the change request specified.
    Caused by ChangesThe incident is caused by the change request specified.
    Master Parent Incident
    The incident has a master incident (a master incident is the opposite of child incidents)parent incident.
    Slave Child IncidentsThe incident has one or more child incidents.
    Related ArticlesThe incident is related to the Knowledge Base article specified.
    Known ErrorThe incident is a known error. It has a recorded root cause and a workaround.
    Related RequestThe incident is related to the service request specified.
    Related EventThe incident is related to the event specified.

    "Parent-child" relationship between incidents
    Anchor
    parent child incident
    parent child incident


    You can create a "parent-child" relationship to link two or more incidents. 

    To make the current incident a parent to another existing incident, complete the following steps:

    1. Navigate to Incident Management → All Incidents and open an incident that you want to be a parent incident.
    2. Open the Related Records tab.
    3. Click the magnifier icon next to the Slave Child Incidents field. The incident list will appear. 

      Tooltip
      onlyIcontrue
      appendIconinfo-filled
      iconColorblue

      You can also use the autosuggest feature when choosing records in Master Parent Incident or Slave Child Incidents. To do so, start typing the incident number or incident subject.


    4. Select the necessary incidents from the list. Click the checkbox icon on the left.
      • You can choose more than one item; all of them will be children for the parent incident.
    5. Click the Select Items button at the top.
    6. The Level of Dependency field is automatically populated with the Master value and remains read-only.
    7. Click Save or Save and Exit to apply the changes.

    To make the current incident a child to another existing incident, complete the following steps:

    1. Navigate to Incident Management → All Incidents and open an incident that you want to be a child incident. 
    2. Open the Related Records tab.
    3. Click the magnifier icon next to the Master Parent Incident field.
    4. Select the incident you want to be the parent for the current incident.
    5. The Level of Dependency field is automatically populated with the Slave value and remains read-only.
    6. Click Save or Save and Exit to apply the changes.

    Tip
    titleParent and Child Incidents

    You can close all child incidents related to the parent incident with a bulk action, without having to navigate to a form of every child incident. To do so, complete the steps below:

    1. Make sure that the parent incident is in the Completed state.
    2. Navigate to the Related Records tab and click the Close all Slave Incidents Complete all child incidents button.

    The state for all child incidents will be changed to Completed, too. The closure notes and other service information will be transferred from the parent incident.

    Also, when you comment on a parent incident, the comment you made is transferred into its child incidents in two ways, depending on the comment type:

    • The comment in the Work Notes field is copied from the parent incident into the relevant fields of all the child incidents.
    • The comment in the Additional CommentComments field is copied from the parent incident into the relevant fields of all the child incidents. A comment announcing notification is sent to the incident caller.

    Create an incident task

    If solving an incident requires participation of various departments, you can create an incident task for each of them. They will be related to the parent incident, but not like in the "parent-child" model. 

    To create an incident task, complete the following steps:

    1. Open the incident you want to work on.
    2. Scroll down the page to Related Lists.
    3. Open the Incident Task tab.
    4. Click New and fill in the fields.

    5. Click Save or Save and Exit to apply the changes.

    You can create as many incident tasks as you need. 

    Incident Tasks form fields

    The date when the assigned person finished the work on this task. The agent should fill in this field.
    FieldMandatoryDescription

    Number 

    YThis field contains an incident task number in INTXXXXXXX format and is populated automatically.
    ParentIncidentYSpecify the incident for which you need to create a task. This field is populated automatically with the number of the parent incidentpopulated automatically when you create an incident task from the related list on the incident form.
    StateNY

    The state of the task. This field is populated automatically. Available options:

    • Registered
    • In Progress
    • Completed
    • Closed
    • Canceled
    Assigned UserSubjectYAdd a short description for the task.
    DescriptionNAdd a detailed description for the task.
    Followers listN

    Specify the users to receive notifications, when:

    • Work note is added to the activity feed; 
    • The record state changes;
    • The value of the fields Assignment Group, Assigned User changes;
    • The agent adds or deletes a follower. 

    The users will not receive notifications when a user Follows or Unfollows the record on their own using a corresponding UI-action on the form. 

    Info

    The field is read-only when the record is in the Canceled or Closed state.

    Choose a person to assign the task to.

    Note

    When an incident has been assigned to a user, the Assignment Group field becomes non-mandatory.

    There is a dependency between the Assigned User and Assignment Group fields. To learn more, refer to Restrictions for assignment

    Assignment GroupY

    Choose a group to assign the task to.

    Note

    When an incident has been assigned to a group, the Assigned User field becomes non-mandatory.

    There is a dependency between the Assigned User and Assignment Group fields. To learn more, refer to Restrictions for assignment

    Notes tab
    SubjectWork NotesYAdd a short description for the task.
    DescriptionNAdd a detailed description for the task.
    Followers ListNContains a list of users subscribed to receive notifications about this task. This field is populated automatically.
    Schedule tab
    Planned Start DatetimeNThe date when the assigned person is supposed to start working on this task.
    Planned End DatetimeNThe date when the task should be Completed or Closed.
    Actual Start DatetimeNThe date when the assigned person started to work on this task. The agent should fill in this field.
    Actual End DatetimeN
    N

    Add work notes. The field becomes mandatory when:

    • the Assigned user changes the state to CompletedCanceled or Closed.
    • other user with the ITSM_agent role changes the State value.

    Follow / Unfollow UI-actions are available on the form. If you click Follow, you will be added to the Followers list and start receiving notifications. If you click Unfollow, you will stop receiving notifications about the changes in the record.

    Access to the form fields


    The read or update access to certain fields of a record can vary depending on the current user's roles.

    • The users with the ITSM_agent or incident_manager roles, other than the creator of the incident task or the assigned user, can:
      • View the record.
      • Submit Work notes in all states of the incident task other than Closed.
      • Edit the Followers list field value.
      • Edit the State, Assignment group, and Assigned user field values in all states of the incident task. The Work notes field becomes mandatory in this case.
    • The caller can:
      • View the record, except for the Work notes field.

    Incident task state model


    Image Added

    Table of Contents
    absoluteUrltrue
    classfixedPosition

    ...