[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-245007-105":53,"doc-detail-245007-en":126},{"code":4,"msg":5,"data":6},0,"success",[7,14,19,24,29,34,39,44,49],{"id":8,"doc_module":9,"doc_module_name":10,"category_name":11,"show_sort_weight":12,"slug":13},11,1,"Template","Presentations",90,"presentations",{"id":15,"doc_module":9,"doc_module_name":10,"category_name":16,"show_sort_weight":17,"slug":18},12,"Resumes",80,"resumes",{"id":20,"doc_module":9,"doc_module_name":10,"category_name":21,"show_sort_weight":22,"slug":23},14,"Invoices",70,"invoices",{"id":25,"doc_module":9,"doc_module_name":10,"category_name":26,"show_sort_weight":27,"slug":28},15,"Posters",60,"posters",{"id":30,"doc_module":9,"doc_module_name":10,"category_name":31,"show_sort_weight":32,"slug":33},16,"Social Media",50,"social-media",{"id":35,"doc_module":9,"doc_module_name":10,"category_name":36,"show_sort_weight":37,"slug":38},17,"Forms",40,"forms",{"id":40,"doc_module":9,"doc_module_name":10,"category_name":41,"show_sort_weight":42,"slug":43},18,"Letters",30,"letters",{"id":45,"doc_module":9,"doc_module_name":10,"category_name":46,"show_sort_weight":47,"slug":48},21,"Paper Templates",5,"papers-templates",{"id":50,"doc_module":9,"doc_module_name":10,"category_name":51,"show_sort_weight":4,"slug":52},158,"General","general-158",{"code":4,"msg":54,"data":55},"ok",{"site_id":56,"language":57,"slug":58,"title":59,"keywords":60,"description":61,"schema_data":62,"social_meta":119,"head_meta":121,"extra_data":123,"updated_unix":125},105,"en","itil-sample-incident-ticket-template-incident-ticket-fields-guide","ITIL - Sample Incident Ticket Template - Incident ticket fields guide","","ITIL incident ticket template text defining the structure of an incident record used in an IT service management tool. It provides an executive overview and an incident overview that explain how incident attributes map to ticket tabs, including field behaviors such as read-only, system generated, linked records, user-defined entries, check boxes, drop-downs, nested drop-down dependencies, and section break markers. It also outlines common ticket details (IDs, contact and location data) and subsequent ticket status, owner, classification, impact, urgency, priority, SLA, and configuration item fields.",{"@graph":63,"@context":118},[64,80,101],{"@type":65,"itemListElement":66},"BreadcrumbList",[67,71,74,77],{"item":68,"name":69,"@type":70,"position":9},"https://docshare.wps.com","Home","ListItem",{"item":72,"name":10,"@type":70,"position":73},"https://docshare.wps.com/template/",2,{"item":75,"name":36,"@type":70,"position":76},"https://docshare.wps.com/template/forms/",3,{"item":78,"name":59,"@type":70,"position":79},"https://docshare.wps.com/template/itil-sample-incident-ticket-template-incident-ticket-fields-guide/245007/",4,{"url":78,"name":59,"@type":81,"image":82,"author":87,"headline":59,"publisher":90,"fileFormat":93,"inLanguage":57,"description":61,"dateModified":94,"datePublished":95,"encodingFormat":93,"isAccessibleForFree":96,"interactionStatistic":97},"DigitalDocument",{"url":83,"@type":84,"width":85,"height":86},"https://docshare.wps.com/thumbnails/itil-sample-incident-ticket-template-incident-ticket-fields-guide/245007.png","ImageObject",442,249,{"name":88,"@type":89},"Cart","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-10-23","2026-09-12",true,{"@type":98,"interactionType":99,"userInteractionCount":8},"InteractionCounter",{"@type":100},"ViewAction",{"@type":102,"mainEntity":103},"FAQPage",[104,110,114],{"name":105,"@type":106,"acceptedAnswer":107},"What is the purpose of the ITIL sample incident ticket template?","Question",{"text":108,"@type":109},"It provides guidance on the attributes and fields to capture in an incident ticket, including how those fields are organized for use in an IT service management tool.","Answer",{"name":111,"@type":106,"acceptedAnswer":112},"What do the different field types mean in this template?",{"text":113,"@type":109},"The template defines read-only, system generated, linked record, user defined, user defined array, check box, drop box, and nested drop box fields, plus visual breaks between sections.",{"name":115,"@type":106,"acceptedAnswer":116},"Which key data elements are captured in ticket details?",{"text":117,"@type":109},"It covers common ticket information such as ticket ID and contact data, followed by status, owner, type, category/subcategory, product type, impact, urgency, priority, SLA, and configuration item details.","https://schema.org",{"og:url":78,"og:type":120,"og:title":59,"og:site_name":91,"og:description":61},"article",{"robots":122,"canonical":78},"index,follow",{"doc_id":124,"site_id":56},245007,1790065653,{"code":4,"msg":5,"data":127},{"doc_id":124,"user_id":128,"nickname":88,"user_avatar":129,"doc_module":9,"category_id":35,"category_name":36,"doc_title":59,"doc_description":61,"doc_content":130,"file_id":131,"file_url":132,"file_type":133,"file_size":134,"view_count":8,"is_deleted":4,"is_public":9,"is_downloadable":9,"audit_status":9,"page_count":135,"language":136,"language_code":57,"site_id":56,"html_lang":57,"table_of_contents":137,"faqs":138,"seo_title":139,"seo_description":61,"update_tm":140,"read_time":73},18829141979164,"https://eur-avatar.wpscdn.com/davatar_6f874abed73319feea01a86fa6f0fab8","ITIL–Sample incident ticket template  \n1. Executive overview  \nDescribe the purpose, scope and organisation of the document.  \n2. Incident overview  \nThis document is intended to provide an understanding of the attributes/fields that need to be captured in an incident ticket (a record of information relating to an incident) .  \nIt provides guidance via several sections which could be considered as different tabs on a ticket within an IT service management tool.  \nThe following definitions apply for the tables below:  \n􀂄 Read only: No data may be entered into the field.  \n􀂄 System generated: The application will automatically generate the correct value(s) .  \n􀂄 Check box: A box, that when clicked will show a mark, indicating that the box has been activated.  \n􀂄 Linked record: Means that the field provides a button to allow the user to click on, which will take them to a list of records in the database, at which point they may choose a value to populate the field with.  \n􀂄 User defined: Field allows the user to enter any value that they wish.  \n􀂄 User defined array: Field is considered a large text box which will allow the user to type multiple lines of text.  \n􀂄 Drop box: Field allows the user to click on a drop down list of information, where they are allowed to make oneselection to populate the field.  \n􀂄 Drop box – nested: The values in this field are dependent on the values listed in the above drop box.  \n􀂄 Break in format: Indicates where there will be a visual break in sets of information captured on the incident ticket.  \n3. Ticket details  \nThis is a common set of information to be gathered for each incident ticket.  \n\n| Field Description (where necessary) Type of field |  |  |\n| --- | --- | --- |\n| Ticket ID | This is the number for the ticket. This should be an incremental number.\u003Cbr>N.B. In high call volume service desks, this number can quickly increase. Some service desks use the following format, which guarantees the number will never exceed a certain length.\u003Cbr>YYYYMMDDxxxxx, where (xxxxx) is a number that resets every day and increments with each new ticket logged. | Read only. System generated. |\n| Contact name | Self explanatory. | Linked record. |\n| First name | Self explanatory. | Read only. Populated by contact name. |\n| Last name | Self explanatory. | Read only. Populated by contact name. |\n\nU C I S A I T I L : S A M P L E I N C I D E N T T I C K E T T E M P L A T E 1  \n| Field Description (where necessary) Type of field |  |  |  |\n| --- | --- | --- | --- |\n| Employee ID |  | It may be necessary to have a unique ID for each contact on the ticket. An employee id is a common solution. | Read only. Populated by contact name. |\n| Email |  | Self explanatory. | Read only. Populated by contact name. |\n| Corporate structure/department |  | This field lists the corporate structure/department that the contact belongs to. | Linked record. |\n| Phone \\# |  | Phone number | Read only. Populated by contact name. |\n| Ext \\# |  | Extension number | Read only. Populated by contact name. |\n| Fax \\# |  | Facsimile number | Read only. Populated by contact name. |\n| Critical user |  | This check box indicates if the user is of some importance within the company and requires a better level of service. | Check box. |\n|  | Break in format |  |  |\n| Reported by different from contact |  | This field is a check box that will display the next section of information.\u003Cbr>This is common amongst tickets, as in some scenarios the person calling about the incident is not necessarily the individual with the issue. For example, Personal Assistant calling on behalf of the CEO. | Check box. |\n| Reported by |  | Name of the person reporting the incident. | Linked record. |\n| Phone \\# |  | Phone number | Read only. Populated by contact name. |\n| Ext \\# |  | Extension number | Read only. Populated by contact name. |\n| Fax \\# |  | Facsimile number\u003Cbr>Break in format | Read only. Populated by contact name. |\n| Location |  | This field should be a ","cbCaioIi3n82u0sd","https://ap.wps.com/l/cbCaioIi3n82u0sd","pdf",222148,6,"English","# Executive overview\n## Purpose, scope and organisation\n# Incident overview\n## Field definitions and tab guidance\n# Ticket details\n## Common information fields\n## Status and classification\n## Configuration item details","[{\"question\":\"What is the purpose of the ITIL sample incident ticket template?\",\"answer\":\"It provides guidance on the attributes and fields to capture in an incident ticket, including how those fields are organized for use in an IT service management tool.\"},{\"question\":\"What do the different field types mean in this template?\",\"answer\":\"The template defines read-only, system generated, linked record, user defined, user defined array, check box, drop box, and nested drop box fields, plus visual breaks between sections.\"},{\"question\":\"Which key data elements are captured in ticket details?\",\"answer\":\"It covers common ticket information such as ticket ID and contact data, followed by status, owner, type, category/subcategory, product type, impact, urgency, priority, SLA, and configuration item details.\"}]","ITIL - Sample Incident Ticket Template - Incident ticket fields guide | PDF",1789224040]