This job aid uses default terms and forms as examples to illustrate how to use specific functions and complete tasks within TDNext. Your unit’s configuration of TDNext may differ from what you see in this job aid. Consult your unit’s training materials and/or your unit administrator for questions or clarifications.
Incident – An ITIL term used to describe an unplanned interruption to an IT Service or a reduction in the quality of an IT Service.
Responsible Group or Individual – A TDX term used to describe the person or persons (group) responsible for proper execution for getting the job done.
Classification – A TDX term used to refer to different kinds of tickets, such as Incident, Service Request, Problem, Change, etc.
Type – A term used to refer to various ticket types that are determined and set up by the user’s unit. Types refer to specific topic areas for tickets within Categories (for example, Category would be "Communication and Collaboration," but the Type would be "Email and Calendar"). Ticket Types can also be associated with specific SLAs, Time Types, and Expense Accounts.
For more TDX terms and definitions, please refer to the Glossary.
TDX includes both Search and Filter functions to help you locate tickets easily in your ticketing application. Depending on which function you use, you can search and/or filter tickets by using ticket IDs, group names, customer names, email addresses, UINs, and NetIDs. This job aid covers the following topics:
TDNext provides a number of “out-of-the-box” options for commonly used filters in the Ticketing application (labeled Tickets) on the left navigation menu. However, if you are looking for a specific subset of tickets not provided by the standard filters, you can use the Filter function. Using the Filter function allows you to filter on many different fields and to save filter searches for future use.
NOTE: Any filtered search where you select multiple filters uses the AND relationship, which only shows tickets where all of the selected criteria are true. To see tickets using the OR relationship, where either one or the other criteria is true, you will need to create a custom report, which is not covered in this job aid.
NOTE: The filter options pane appears from the right listing all the ticket fields associated with the ticket type.
NOTE: The Filter pane contains many fields by which you can search. The default view of the Filter pane shows the Standard Fields, which are grouped into several categories, including General, Responsibility, Priority Factors, Dates/Updates and several others that can be viewed by scrolling down the panel. Some of the Standard Fields listed under the General category at the top of the Filter pane include Text Search, ID, Requestor, Acct/Dept(s), Ticket Type(s), and Current Status.
Some fields will be custom and can only be found by selecting theCustom Fields tab at the top of the Filter pane. Use the righthand scroll bar to navigate to the options you want to select. The Scroll button at the top of the Filter pane provides a drop-down menu that lists the standard categories of all fields, allowing you to quickly get to a section without using the scroll bar.
NOTE: You may make selections in multiple fields. Keep in mind that selecting multiple fields uses the AND relationship in the search.
NOTE: Any results for your filter selections appear in the Tickets window.
The ID/Search box in the upper right corner of the Ticketing application allows you to quickly search for tickets using several different data points, such as the ticket ID number, Status, Classification, orResponsible Group. Note that using the ID/Search function may bring up any tickets that have a history of being connected to your search term. For example, if you search by a Responsible Group or Person, the search results here may include tickets that had once been assigned to that Group or Person and have since been reassigned, or tickets that have been read or reviewed by that Person or Group.
NOTE: To search for tickets using Requestor UIN or NetID, you must use the People application.
If you know the ticket ID number, you can use the ID/Search box in the top right corner of the Ticketing application to search for the ticket.
NOTE: This opens the ticket if it is found. If the ticket is not located, the Ticket Not Found window appears.
NOTE: This displays a list of tickets connected to that Group if there are any.
NOTE: Unlike the People app, you cannot search for UIN or NetID using the ID/Search function.
TDNext allows you to save filtered searches you create so you can quickly use them again.
NOTE: Searches that are created and saved within a specific ticket classification on the left menu (such as Incidents or Service Requests) will only be available when you are using that ticket classification. Searches created when using the main Ticketing application or any of the “out-of-the-box" options will be available across all options and ticket classifications.
NOTE: The Save Search window opens.
NOTE: If applicable, click the checkbox next to Global, which will allow this search to be accessible to any user of the Ticketing application. Follow your unit’s guidance and naming conventions for global searches
NOTE: This saved search now appears in the My Saved Searches drop-down menu at the top of the Tickets window.
To access your saved searches, be sure to select the correct option from the left menu. Remember that searches created within specific ticket classification on the left menu (such as Incidents or Service Requests) will only be available when you are using that ticket classification.
NOTE: The search will automatically run, and the results will appear in the Tickets window.