<style>p { margin: 0; }span.fr-emoticon.fr-emoticon-img { background-repeat: no-repeat !important; font-size: inherit; height: 1em; width: 1em; min-height: 20px; min-width: 20px; display: inline-block; margin: -0.1em 0.1em 0.1em; line-height: 1; vertical-align: middle; } span.fr-emoticon { font-weight: normal; font-family: "Apple Color Emoji", "Segoe UI Emoji", "NotoColorEmoji", "Segoe UI Symbol", "Android Emoji", "EmojiSymbols"; display: inline; line-height: 0; } blockquote { border-left: solid 2px #5e35b1; color: #5e35b1; margin-left:0; padding-left:5px;}blockquote blockquote{ border-color: #00bcd4; color: #00bcd4;}blockquote blockquote blockquote{ border-color: #43a047; color: #43a047;} table.grid{ border-collapse: collapse;} table.grid td, table.grid th { border: 1px solid #ddd;} .fr-fic.fr-dib{ display: block; margin: 5px auto;}.fr-fic.fr-dib.fr-fir{ text-align: right; margin: 5px 0 5px auto;}.fr-fic.fr-dib.fr-fil{ text-align: left; margin: 5px auto 5px 0;}.fr-fic.fr-dii{ float: none; margin: 5px auto;}.fr-fic.fr-dii.fr-fil{ float: left; margin: 5px auto;}.fr-fic.fr-dii.fr-fir{ float: right; margin: 5px auto;}img.fr-dib.fr-fir { margin-right: 0; text-align: right;}img.fr-dib.fr-fil { margin-left: 0; text-align: left;}img.fr-dib { margin: 5px auto; display: block; float: none;}img.fr-bordered { box-sizing: content-box; border: solid 5px #CCC;}img.fr-shadow { box-shadow: 10px 10px 5px 0px #cccccc;}img.fr-rounded { border-radius: 10px; -moz-border-radius: 10px; -webkit-border-radius: 10px; -moz-background-clip: padding; -webkit-background-clip: padding-box; background-clip: padding-box;}</style><style>
p {
margin: 0;
}
span.fr-emoticon.fr-emoticon-img {
background-repeat: no-repeat !important; font-size: inherit; height: 1em; width: 1em; min-height: 20px; min-width: 20px; display: inline-block; margin: -0.1em 0.1em 0.1em; line-height: 1; vertical-align: middle;
}
span.fr-emoticon {
font-weight: normal; font-family: "Apple Color Emoji", "Segoe UI Emoji", "NotoColorEmoji", "Segoe UI Symbol", "Android Emoji", "EmojiSymbols"; display: inline; line-height: 0;
}
blockquote {
border-left: solid 2px #5e35b1; color: #5e35b1; margin-left: 0; padding-left: 5px;
}
blockquote blockquote {
border-color: #00bcd4; color: #00bcd4;
}
blockquote blockquote blockquote {
border-color: #43a047; color: #43a047;
}
table.grid {
border-collapse: collapse;
}
table.grid td,
table.grid th {
border: 1px solid #ddd;
}
.fr-fic.fr-dib {
display: block; margin: 5px auto;
}
.fr-fic.fr-dib.fr-fir {
text-align: right; margin: 5px 0 5px auto;
}
.fr-fic.fr-dib.fr-fil {
text-align: left; margin: 5px auto 5px 0;
}
</style><p><strong>In this guide we will cover:</strong></p><p><strong>- What are Ticket Types? </strong></p><p><strong>- Creating a Ticket Type</strong></p><p><br></p><p><br></p><p><strong>Admin Guides:</strong></p><ul><li style="font-weight: bold;"><a href="https://usehalo.com/haloitsm/guides/2055/" target="_blank" rel="noopener noreferrer"><strong>Ticket Types</strong></a></li></ul><p><strong><br></strong></p><p><strong>Related Guides:</strong></p><ul><li><a href="https://usehalo.com/haloitsm/guides/933/" target="_blank" rel="noopener noreferrer"><strong>Modifying and Adding Workflows</strong><br></a></li><li><a href="https://usehalo.com/haloitsm/guides/1927/" target="_blank" rel="noopener noreferrer"><strong>Service Level Agreements (SLAs)</strong><br></a></li><li style="font-weight: bold;"><a href="https://usehalo.com/haloitsm/guides/1929/" target="_blank" rel="noopener noreferrer"><strong>Statuses</strong></a></li></ul><p><br></p><p><strong><em>Note: We cover a lot of the most used settings in this guide, but there are a lot more options. For detail on what each setting here does, check out the linked admin guide.</em></strong></p><p><br></p><p><strong><span style="font-size: 14pt;">What are Ticket Types?<br></span></strong></p><p>Ticket types are individual kinds of ticket that can be created for different purposes. It is a way of categorising your tickets as well as by setting ITIL types against a certain ticket type.</p><p><br></p><p><strong><span style="font-size: 14pt;">Creating a Ticket Type</span></strong></p><p>Head to Configuration > Tickets > Ticket Types.</p><p><br></p><p><span style="font-family: Arial,Helvetica,sans-serif;"><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjY3OTc5M2I5LTUyZGQtNGNkOC1hMzEyLTlkNWQ1OTk2ZmM3NCJ9.0SfnzxZ9s8Rh4Rla8PNV4IlCCHMfLDvwcV1ux4wCw0U" class="fr-fic fr-fil fr-dib" width="773" height="194"><strong><span style="font-size: 10pt;">Fig 1. Ticket Types configuration.</span></strong></span></p><p><br></p><p><span style="font-family: Arial,Helvetica,sans-serif;">Click on an existing ticket type and "Edit" to change an existing ticket type, or click "New" to create a new one. The following details how to create a new ticket type, but the same steps apply when editing.</span></p><p><br></p><p><span style="font-family: Arial,Helvetica,sans-serif;">The "Details" tab will open by default.</span></p><p><span style="font-family: Arial,Helvetica,sans-serif;"><br></span></p><ul><li style="font-family: Arial, Helvetica, sans-serif;">Give your new ticket a name ("Ticket Type Name") and set the ITIL type ("ITIL Ticket Type").</li><li style="font-family: Arial, Helvetica, sans-serif;">Set the "Use" to Tickets.</li><li style="font-family: Arial, Helvetica, sans-serif;">The check-boxes below this can be amended as you need based on who you want to have access to this ticket type.</li><li style="font-family: Arial, Helvetica, sans-serif;"><a href="https://halopsa.com/guides/article/?kbid=1893" rel="noopener noreferrer" target="_blank">Ticket Groups</a></li><li style="font-family: Arial, Helvetica, sans-serif;"><a href="https://usehalo.com/haloitsm/guides/1341" rel="noopener noreferrer" target="_blank">Tickets General Settings in Detail</a></li></ul><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjdmNDU5YjFlLWEzMDctNDM4NS05YjkxLTgyNzc4ZDY0NzA1MiJ9.k1lCAyLubz93BA7XaOZqUwo9uE416xYfbxpeKZb95VY" class="fr-fic fr-fil fr-dib" width="1232" style="width: 1234px; height: 584.492px;" height="584"></p><p><strong><span style="font-size: 10pt;">Fig 2. Details tab on a ticket type.</span></strong></p><p><br></p><p>The next tab is the "Defaults" tab. This is where you set the "Initial Status" of the ticket when it is first opened, and whether the ticket should automatically start a workflow or approval process. </p><p>You will also need to set the team/agent it should be assigned to by default, and the email "From Address" to use.</p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjhmZDE0ZDIwLTlmZjgtNDBkZi1iY2M5LTA1OGFlMDVjZTFhOCJ9.PGMVAsuUcvMUOpUZUyLnYe_TSm5fAk61D0YTChTJPus" class="fr-fic fr-fil fr-dib" style="width: 1230px; height: 578.106px;" width="1228" height="578"></p><p><strong><span style="font-size: 10pt;">Fig 3. Defaults tab on a ticket type.</span></strong></p><p><br></p><p>The "Forms" tab is next, which can be used to customise how the ticket is logged by end-users in the self-service portal, as well as how the ticket appears on the agent portal. For instance to show the "Audit Log" tab, enable "Display the Auditing Tab". This will show all changes made to that ticket by both system and agents, which will allow you to understand when/why a change was made.</p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjQ0NDJkMjY5LWFmOGEtNDc0Ni04YzJjLTQzMTE4NGUxNWJkYSJ9.p19mJFsy3sbaSiaaSkN6TWxGhRoQp0tcqXUd4s9oOpo" class="fr-fic fr-fil fr-dib" width="1225" style="width: 1227px; height: 579.221px;" height="579"></p><p><strong><span style="font-size: 10pt;">Fig 4. Forms tab on a ticket type.</span></strong></p><p><br></p><p data-pasted="true">From v2.238+, Ticket Details in the Agent Application can be shown at the top of a Ticket. To enable this select the "Show Details at the top of the Ticket option in the Forms tab. </p><p><br></p><p>The "Field List" tab is where fields can be added to the ticket type - both custom and system. Just click the "Add" button and select some from the dropdown list. Below, the "Asset" field has been added for example, which will allow agents to link related assets to the ticket.</p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjhiOTAwNWI4LTUzY2ItNDU2NS1hOTQwLTY1ZmIwZDZlZDdiYSJ9.I6SXs54k3Jcwjav2sXRxq8mnbzsO1Vhu9BTWl5prf3A" class="fr-fic fr-fil fr-dib" width="1228" style="width: 1230px; height: 581.315px;" height="581"></p><p><strong><span style="font-size: 10pt;">Fig 5. Field List tab on a ticket type.</span></strong></p><p><br></p><p>Clicking the pencil icon on a field will allow you to edit the field visibility. You can set whether it shows for agents and/or users, and whether it is mandatory.</p><p><br></p><ul id="isPasted"><li style="font-family: Arial, Helvetica, sans-serif;"><strong>End-User New ticket </strong>- Visibility for new tickets raised via your End-User Portal</li><li style="font-family: Arial, Helvetica, sans-serif;"><strong>End-User Ticket Details</strong> - Visible on Existing tickets on End-User Portal</li></ul><p>It then works similarly for Agent visibility.</p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjAzNDEwZTdjLWIxODctNDA1Ny05YTk0LTZlZmU4ZDFhMzAyZiJ9.FqRPfuLpu5VHRQZaFVGCaiONwHyOdPYwbbkCIeaRFcw" class="fr-fic fr-fil fr-dib" style="width: 1228px; height: 576.904px;" width="1226" height="577"></p><p id="isPasted"><strong><span style="font-size: 10pt;">Fig 6. Setting if the field is mandatory/visible. </span></strong></p><p><br></p><p><span style="font-family: Arial,Helvetica,sans-serif;">Scrolling down on the popup will show the options for dynamic visibility.</span></p><p><br></p><ul><li><span style="font-family: Arial,Helvetica,sans-serif;"><strong>Dynamic Field Visibility</strong> - This field will only show based on the conditions set here based on another field.</span></li><li><span style="font-family: Arial,Helvetica,sans-serif;"><strong>Dynamic Field Value Visibility</strong> - Values within this field will only show based on the conditions set here.</span></li></ul><p><span style="font-family: Arial,Helvetica,sans-serif;">This can be used for creating a process whereby filling in one field makes another appear, this is useful when making a ticket type which acts as a questionnaire for example.</span></p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjhjMmNjZDVmLTAzM2ItNGQ0NS1iOGJlLWE1YzRiMzY2NTYxZSJ9.CghqSxpsEAGRsHAU1MXvCX5zB47QLU522wQucIG9_ls" class="fr-fic fr-fil fr-dib" width="1225" style="width: 1227px; height: 576.396px;" height="576"></p><p><strong><span style="font-size: 10pt;">Fig 7. Dynamic visibility options.</span></strong></p><p><br></p><p>If creating a new ticket type, the "Layout" tab will appear greyed out. It will become available once the ticket type has been created and saved. This will automatically be set to "Default", but if you wish to move around the order of the tabs on the ticket type, set this to "Custom" where you can drag-and-drop to rearrange, or edit to hide tabs.</p><p><br></p><p>You will also noticed that once saved, the option for "Access Control" appears in the buttons at the top. Here, administrators can grant access for other agents to be able to modify the configuration of the specific ticket type. This is a useful feature so that managers can edit the ticket type that their team uses without having to ask the administrator to do it foe them.</p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImIxNjY3NzYyLWI5ZWEtNDJmMi1iZDM2LWE5OWMxNGZjYmM2YyJ9.SXFqoLVU15vHxN_WW5YQX3a8DmXRKkMcVmpgep82pxA" class="fr-fic fr-fil fr-dib" width="1230" style="width: 1232px; height: 580.635px;" height="581"></p><p><strong><span style="font-size: 10pt;">Fig 8. Layout tab.</span></strong></p><p><br></p><p>The "Allowed Values" tab dictates which statuses, actions, etc, are available for use on the ticket type. If checked to allow all, the only restrictions will be by agent permission or the workflow. If unchecked, a table will appear where you will have to manually add each value you wish to allow. From v2.238+, available Canned Texts can be restricted using this method. </p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjBmMmIzNjQyLTNkMDYtNDNjNS04ZmRhLTllNTQyYTdhMGU5NyJ9.NTxgzj-FIo-lUbh7m_nj9q8P1uFlnf9Ki6nWGRFiQ_8" class="fr-fic fr-fil fr-dib" width="1228" style="width: 1230px; height: 580.976px;" height="581"></p><p><strong><span style="font-size: 10pt;">Fig 9. Allowed Values tab on a ticket type.</span></strong></p><p><br></p><p><span style="font-family: Arial,Helvetica,sans-serif;">The final tab, "Settings", is where the status after action, closure, and email settings are configured.</span></p><p><br></p><p>The "Status After Action" sets what the status of the ticket will be after certain people respond, i.e. "Status after End-User update" is usually set to "Updated" to show agents that the user has responded.</p><p><span style="font-family: Arial,Helvetica,sans-serif;"><br></span></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjgzODYzOTg2LTY3ZjktNGI0My1iOTBkLWVlYzkxYWZlOWFkOCJ9.HwPvrGu0ddzOTmo9uRjbqGa9d9q4uOardHQyn8Vder4" class="fr-fic fr-fil fr-dib" style="width: 1231px; height: 577.292px;" width="1229" height="577"></p><p><strong><span style="font-size: 10pt;">Fig 10. Settings > Status After Action on a ticket type.</span></strong></p><p><br></p><p>Further down is the "Email" section. The key settings here are whether you enable SLA hold reminders, enable account manager emails, or if the ticket CCs in followers.</p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImVjNmI2MjRlLTk0OGMtNDkxMC05NmQ0LWVlYmRmMWRiODc2NyJ9.XFSBqfvmZsroYWw9P_Pph5dfvViCeOZoLITj6ryVzSU" class="fr-fic fr-fil fr-dib" width="1228" style="width: 1230px; height: 577.766px;" height="578"></p><p><strong><span style="font-size: 10pt;">Fig 11. Settings > Email on a ticket type.</span></strong></p><p><br></p><p>Scrolling down a bit further is where the "Closure settings" are contained. Here is where you can configure whether emails on closed tickets reopen them or not, whether children need to be closed to close the parent, or if you are using closure confirmation procedures.</p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjFmNjdhM2NkLTIwMzgtNDA5OS05MzdkLTQyY2VmZTA3ZjA5YyJ9.1z1dS3f_5LGnMUtlno0pm96RTzFlrsKaM9Hvi5eYHX4" class="fr-fic fr-fil fr-dib" width="1224" style="width: 1226px; height: 578.785px;" height="579"></p><p><strong><span style="font-size: 10pt;">Fig 12. Settings > Closure settings on a ticket type.</span></strong></p><p><br></p>
