GUIDE STATUS:
| Status | ||||||
|---|---|---|---|---|---|---|
|
- Input into the filter navigator, "Create New"
- Under Incident, Click on Create New
⚠️ WARNING: Non-UCI callers will NOT receive relevant emails with new incidents automatically. You must add them to the incident's watch list. To do this, visit Add Non-UCI Callers to Watchlist.
GLOSSARY FOR ALL FIELDS:
| Field | Describes |
|---|---|
| Caller | Person or group experiencing issue. |
| Category | Source of issue. |
| Subcategory | More specifically designed origin of issue. |
| Configuration Item | Most specific issue origin. |
| Impact | The number of people affected as it relates specifically to this issue. ⚠️ Do not assume the impact of the incident upon creation. Report it exactly how the caller describes it. For more details, please view: Impact Levels |
| Urgency | How much of an impact issue has on caller's operations. For more details, please view: Urgency Levels |
| Priority | Thelowernumber The lower number of the impact and urgency level. |
| Number | ID of incident. For efficiently searching for incident. |
| Opened | Date when incident was incident report. |
| Opened By | Employee that created incident report. |
| Contact Type | How caller communicated issue. |
| Assignment Group | Internal OIT group that is tasked with dealing with incident. |
| Assigned to | Specific employee tasked with solving incident. |
| State | Status of the incident. For more details, please view: Incident States |
| Short Description | Describe the core issue the caller is experiencing, along with any information that caller believes is contributing to issue. |
Update Log
| Updated By | Date | Notes |
|---|---|---|
| Alexander Braxton Awest | In review | |
| Alexander Braxton Awest | Initial Creation and first draft complete. |