Via the Self-Service Portal
This procedure is available for all end-users.
To create an incident, complete the steps below:
- Navigate to your Portal main page.
- Click Report an incident and fill in the fields.
- Click Save.
New incident form fields
| Field | Mandatory | Description |
|---|---|---|
| Urgency | Y | Specify the urgency of the request. Typically, it is evaluated based on the time remaining until the incident impacts the business. |
| Subject | Y | Add a brief description of the incident. |
| Description | N | Add a detailed description of the incident. |
You can also attach some files by using the attachment window. To add files, drag them to the attachment window, or click Upload from computer and select them on your device.
You can track the work process on the My Tickets page. To open the record of the incident, complete the following steps:
- In the header, navigate to Cabinet → My Tickets.
- Click My Incidents on the left.
- Check the state of the created incident.
Also, you can see more information about the incident by clicking the number.
Via the agent interface
Role required: ITSM_agent or admin.
To create an incident, complete the steps below:
- Navigate to Incident Management → New.
- Fill in the fields.
- Click Save or Save and exit to apply the changes.
New incident form fields
The incident number has the INCXXXXXXX format and is populated automatically.
| Field | Mandatory | Description |
|---|---|---|
| General tab | ||
| State | Y | Specify the work state and progress of the incident. See the Process Incidents article to learn more. |
| Resumption of work | Y | This field appears if the incident is in the Postponed state. Indicate the date and time when the work on the incident must be resumed. |
| External task | N | Specify the task to do for the external company. The field appears on the form when the state is External processing. If the field is populated, it is displayed in other states. |
| External company | N | Specify the company that works on the incident task externally. The field appears on the form when the state is External processing. If the field is populated, it is displayed in other states. |
Impact | Y | Measure the impact caused by the incident on the business processes. When the Major incident checkbox is selected, the value of this field is changed to Very high. See the Priority Management article to learn more. |
| Urgency | Y | Specify the urgency of the request. Typically, it is evaluated based on the time remaining until the incident impacts the business. See the Priority Management article to learn more. |
| Priority | Y | Identifies the importance of the incident. This field is populated automatically based on the value of the Impact and Urgency fields. See the Priority Management article to learn more. |
| Assignment group | Y | Specify the group assigned to work on the incident. This field is non-mandatory if the Assigned User field is filled or the State is In progress, Completed, or Closed. There is a dependency between the Assigned user and Assignment group fields. See the Auto Assignment article to learn more. |
| Assigned user | Y | Specify the user assigned to work on the incident. This field is non-mandatory if the Assignment group field is filled and the State is not In progress, Completed, or Closed. To reassign a user or a group, use the Reassign button at the top right corner of the window, or assign another user, or a group by clicking the magnifier icon next to the Assigned user field. As a result, the incident state changes to Assigned. There is a dependency between the Assigned user and Assignment group fields. See the Auto Assignment article to learn more. |
| Subject | Y | Add a brief description of the incident. After saving, the field is hidden on a form. |
| Description | N | Add a detailed description of the incident. If the Infrastructure incident checkbox is selected, this field becomes read-only after the record is created. |
| Steps to reproduce | N | Specify the steps to reproduce the incident. |
| Screenshot | N | Upload screenshots supporting the incident, if any. |
| Related CIs | N | Specify the related configuration items affected by the incident. |
| Caller | Y | Specify the originator of the incident. |
| Company | N | Specify the company to which the incident is related. |
| Service | Y | Specify the service affected by the incident. |
| Contact type | Y | Select the source from which the request is received. Available options:
When the Infrastructure Incident checkbox is selected, the available options change to:
The incidents with the Contact type set to Monitoring can be automatically created by an integrated monitoring system via Monitoring and Event Management. When the record is saved, this field becomes read-only. |
| Infrastructure incident | N | Select this checkbox to create an infrastructure incident. When the record is saved, this field becomes read-only. |
| Major incident | N | Select this checkbox to categorize the incident as a major incident.
|
| Attention required | N | Select this checkbox to notify the line manager of the assigned group/assigned user. |
Activity Feed | ||
| This section appears after the incident is saved. | ||
| Additional comments | N | Write a comment with additional information about the incident. |
| Work notes | N | Add any work notes that may be useful. |
| Related Records tab | ||
| Use this tab to relate incidents to other types of tasks. See Create Records Related to Incidents to learn more. | ||
Closure Information tab | ||
| This tab appears when the incident state is Completed. See Process Incidents to learn more. | ||
| Followers List | ||
| This field is populated automatically with a list of users who follow the incident for tracking the updates. This field is read-only for any users without the ITSM_agent role. | ||
The External Specification and Internal Specification related lists contain Knowledge Base articles with the same Service as in the incident, for quick access to the necessary instructions. See the Knowledge Management article to learn more about the service specifications.
Create an infrastructure incident
Role required: ITSM_agent or admin.
An infrastructure incident is an incident created by service agents of the 1st or the 2nd levels or by the integrated monitoring system.
To create an infrastructure incident, complete the steps described above, and select the checkbox Infrastructure incident.
You can categorize an infrastructure incident as a major incident. To do so, select the Major incident checkbox.
A major incident is an incident of the highest impact and highest urgency. It affects many users, depriving them of vital business functions. Major incidents have a separate procedure with shorter time scales. Major incidents require many people of various hierarchy levels to be involved. A major incident is always an infrastructure incident.
When the Major incident checkbox is selected, the Impact field value is changed to Very high.
If an infrastructure incident is categorized as a major incident, a new tab, Chronology, is displayed next to the Related Records tab on its form.
Swarming session on a major incident
To enable the functionality of the Swarming Session, complete the settings described in the Set up Telegram Swarming Session article.
Swarming Session is a temporarily created group in Telegram designed to speed up the work on major incidents. Once joined, the members of the group collaborate on the incident faster and more effectively. All the updates done on the incident form (new states, comments, and changes in other fields) are copied to the group automatically. The comments from the Telegram group are also copied to the incident Activity Feed on behalf of Guest User. The work note indicates the name of the specific Telegram user who left the comment. When the incident state changes to Completed, commenting becomes impossible, and when the state changes to Closed, the group disappears.
To initiate the Session:
- Click the Start Swarming button on the top of the page.
- In a new window that appears, verify the list of the participants responsible for the incident management, add or remove any if necessary. These people will receive an email invitation to join a Telegram group devoted to the major incident. By default, the recipients are: Assigned User, Incident Manager and Service Owner. The user who clicked Start Swarming becomes the initiator of the session and also receives the invitation even though their name is not in the list.
Apart from the email invitation, a link to the Telegram group is available on the incident form, above the Activity Feed. Share the link with any associated with the incident people, even if they are not the SimpleOne users. Their comments will also be transferred to the Activity Feed.
After the incident is closed, the link disappears.
Create an incident from a user query
Role required: incident_manager.
A user query is an entity of a more abstract level than an incident. To create an incident from a user query, complete the steps below:
- Navigate to User Queries → All User Queries.
- Open the user query you want to create an incident from.
- Click the Incident button in the top-right corner of the form.
When you create an incident from a user query, they are linked to each other:
- The reference to the incident is displayed in the Related ticket field of the user query.
- The reference to the user query is displayed in the Related Records tab of the incident.
You can only create an incident from an unprocessed user query. If an incident, problem, change request, or service request has already been created from a user query, the buttons shown above are hidden from the form.
