Ticket Fields
Tickets fields vary depending on the Ticket Type of a Ticket that is created. The 3 problem management ticket types use the same pool of required fields, with the detailed fields being more important as the problem ticket type escalates.
Project tickets require fewer fields on the encompassing ticket. This is because most of the relevant ticket information for project tickets is saved in the project ticket's Project Tasks.
Change Management Request tickets require a different pool of fields to save information related to the change. These fields include: Business Impact, Change Steps, Back Out Plan, Planned Start and Planned End.
Ticket Fields
FIELD | TASK | EVENT | PROBLEM | PROJECT | CMR |
---|---|---|---|---|---|
Title | Req | Req | Req | Req | Req |
Description | Req | Req | Req | Req | Req |
Date Occurred | Req | Req | Req | No | No |
Customer | Req | Req | Req | Req | Req |
Location | Req | Req | Req | Req | Req |
Area | Req | Req | Req | Req | Req |
Customer Contact | Yes | Yes | Yes | No | Yes |
Contract | Req | Req | Req | Req | Req |
Primary Equipment | Yes | Yes | Yes | No | Yes |
Secondary Equipment | Yes | Yes | Yes | No | Yes |
Activity | Yes | Yes | Yes | No | Yes |
Customer Contact | Yes | Yes | Yes | No | Yes |
Production Impacting | Yes | Yes | Yes | No | No |
Top Issue | Yes | Yes | Yes | No | No |
Root Cause | Yes | Yes | Yes | No | No |
Downtime Minutes | Yes | Yes | Yes | No | No |
Status | Req | Req | Req | No | Req |
Time Spent | Req | Req | Req | no | Req |
Time Spent Off Hours | Yes | Yes | Yes | No | Yes |
Analysis | Yes | Yes | Yes | No | No |
Next Steps | Yes | Yes | Yes | No | No |
Resolution | Yes | Yes | Yes | No | No |
Teams Assigned | Req | Req | Req | Req | Req |
Engineer Assigned | Yes | Yes | Yes | No | Yes |
Attachments | Yes | Yes | Yes | No | No |
Business Impact | No | No | No | No | Req |
Change Steps | No | No | No | No | Req |
Back Out Plan | No | No | No | No | Req |
Planned Start | No | No | No | No | Req |
Planned End | No | No | No | No | Req |