Already a NinjaOne customer? Log in to view more guides and the latest updates.

NinjaOne Ticketing: Anatomy of a Ticket

Topic

This article explains how to navigate and use the fields within a ticket in NinjaOne.

Environment

NinjaOne Ticketing

Description

When you open a ticket to begin working on it, there are numerous modifiable fields and tools. Understanding these tools will empower you to get the most out of our ticketing solution.

Select a category to learn more:

Ticket Action Menus, Tabs, and Filters

The header of a ticket contains the name of the ticket and its creation date, and several menu options. The following table describes the function of all fields in this area.

NumberFeature Description
1This text shows the name and number of the ticket. Click the star to add the ticket to your Favorites list.
2
  • Click the Options menu to split, merge, export, or delete a ticket. To learn more about these actions, refer to NinjaOne Ticketing: Manage Your Tickets.
  • Click Apply template to use a ticketing template.
  • Click Save to record changes to the ticket.
3
  • Overview: The main details of the ticket and the default view.
  • Related Tickets: Link a ticket to another ticket.
  • Products: Add new, existing, or non-catalog products to the ticket. These may include hardware requests or billed labor. Use the filters at the top of the table to find specific product types, statuses, or technicians.
    • New: Create details for a new product.
    • Existing: Select active products that you previously created.
    • Non Catalog: Create details for an "ad hoc" product. These products will not be added to the list of your existing products.
4
  • Status: Select a new ticket status from this drop-down menu. Manage ticket statuses at AdministrationAppsInstalledNinjaOne TicketingCustom Status.
  • Type: You can select the ticket type at the time of creation and change this data at any time.
  • Form: You should select the ticket form at the time of creation. Each form contains a configured set of fields that guide the requestor in providing necessary information depending on the subject. Manage ticket forms at AdministrationAppsInstalledNinjaOne TicketingForms.
5This area shows the date of ticket creation and how the ticket was created (either automated or manually by a user).
ticket_top.png
Figure 1: Ticket action menus, tabs, and filters

Related Tickets

The Related Tickets tab allows you to link tickets or assign them to a parent (top-level) ticket. This tab will appear after you save a newly created ticket. You can also use this tab to reassign linked incidents to different problems.

  • Add related ticket: Link any ticket to any other ticket. You can link multiple tickets at a time. After linking a ticket, click the button again to link another.
related tickets_add related ticket.png
Figure 2: Link a ticket to another ticket
  • Assign parent ticket: Select a ticket to assign as a parent. You can only assign one ticket as the parent. If you assign a parent ticket and then click Assign parent ticket again, any ticket you select will replace the original assignment.
related tickets_assign parent ticket.png
Figure 3: Assign a parent ticket 
  • Remove a related ticket: Select the checkbox next to the related ticket and then click Remove. You can only remove one relationship at a time.
ticketing_remove related tikcet.png
Figure 4: Remove a related ticket 
If you link a ticket and later assign it as the parent, the parent relationship will override the link and update the relationship, if applicable. The Parent tag will display next to the ticket status. Once assigned as a parent, you cannot change the parent ticket relation to a different relationship type.

When linking to another ticket or assigning a parent, define the relationship between the tickets by selecting an option from the Ticket Relationship drop-down menu. If you need to create a new relationship, you can do so from the NinjaOne Ticketing configuration page at Custom Relationships if you have the appropriate permissions. Refer to NinjaOne Ticketing: Setup and Configuration to learn more.

related tickets_link_relationship.png
Figure 5: Add a relationship to linked tickets (click to enlarge)

Requester

The Requester section of the ticket provides the responsible organization, the name of the individual who requested the ticket (if not created via automation), the affected device, and the agreement service if applicable. Click Edit to modify these fields. The organization that you select will determine what data appears in the related drop-down menus; technicians and end users who belong to other organizations will not appear.

After you enter data into the fields, you can take the following actions: 

  • Click the organization or location name to navigate to its dashboard.
  • If the requester is a technician, click the name to navigate to their account page. If the requester is a contact, click the name to view or edit contact information. If the requester is an end user, click the name to the end user's dashboard.
  • Click the device name to navigate to the device's dashboard. Click the action button to view available actions that you can take on the device.
ticket requester.png
Figure 6: Ticket Requester section

Details

The Details section of a ticket allows you to assign attributes to the ticket, such as the technician responsible for ticket resolution, priority or severity, and other custom fields required by the ticket form in use.

When viewing a ticket without an assignee, technicians can quickly assign the ticket to themselves by clicking Assign to me. This button is only visible when there is no assignee. You can click the X to the right of the current assignee's name to remove them, and the Assign to me button will display on the ticket page.
Use the Additional Assignees field to add multiple technicians to the ticket for visibility and collaboration.

ticket details.png
Figure 7: Ticket Details section

Public Response and Private Note

The response panel allows technicians to publish public responses and private notes. The requester and CCs will receive notification of new public responses via email, unless the ticket requestor posted the response. Only technicians can view private responses. You can manage email notifications at AdministrationAppsInstalledNinjaOne TicketingGeneralSystem Email Notifications.

The timer in the response window indicates how long the ticket has been worked and either starts automatically when you click inside the response field, or can be manually started, depending on the general ticketing settings. You can configure these settings at AdministrationAppsInstalledNinjaOne TicketingGeneralSettings. This timer may be paused at any time, edited, or reset. To edit or reset it, open the action menu next to the timer. The timer will also reset when publishing a response or note.

ticket response.png
Figure 8: Public response for a ticket

When you type in the text field, whether as a Public Response or Private Note, the Save button in the top-right corner of the ticket will change to a Publish button. If you also made changes to any modifiable field, those changes will be published concurrently with the response or note.

  • NinjaOne will automatically spellcheck responses and notes, and will underline typographical errors.
  • NinjaOne will scan attachments and trigger an activity if infected or suspicious attachments are found. You can configure the activity to send notifications to technicians, a notification channel, or create a ticket. To configure notifications, navigate to AdministrationGeneralActivities and turn on notifications for the Attachment File Suspicious activity.
  • Technicians may tag other technicians within ticket responses. Tags will automatically send an email notification to that technician. Technicians do not receive emails when tagging themselves.
    • If a technician tags another technician who does not have access to that ticket, an icon and tooltip will be displayed to indicate the missing requirement.
    • If a tagged technician is deleted from NinjaOne, an icon and tooltip will be displayed to indicate that information.
  • When you add a Public Response to a parent ticket, you can publish the response to all linked tickets.
    • The Public Response feature is not available on tickets that are not designated as "parent."
    • By default, all linked relationships are selected when the checkbox is selected. You can remove relationships by clicking the X.
publish response to all child tickets.png
Figure 9: Publish response to all child tickets

Link Other Tickets within a Response

Technicians with the appropriate permissions can use the response feed to link to other existing tickets by using the hash (#) function followed by the ticket number. Use this method for non-incident or problem tickets that may be used to link an ongoing investigation or refer to a workflow.

link tickets.png
Figure 10: Link or refer to tickets within a comment

If the ticket number is a valid format, it displays as a hyperlink in the feed. However, if the ticket number is not correct, clicking the link will result in a Ticket Not Found notification.

Ticket Activity

This panel displays all information about changes to the ticket as well as responses.

  • Filter Type to show public responses, private notes, system activity, or any combination of those three.
  • Filter Sort by to organize the feed by either newest or oldest.
ticket activity.png
Figure 11: Ticket activity

Recent Tickets

Recent tickets are open tickets that share the same organization, user, device, or location. Only the five most recent tickets are displayed by default; click View more tickets to expand the search.

Move your cursor over the subject to preview the recent ticket data. Use the drop-down menu or click View more tickets to review:

  • Organization: See other tickets assigned to the same organization.
  • Location: See other tickets assigned to the same location.
  • User: See other tickets requested by the same user.
  • Device: See other tickets assigned to the same device.
recent ticket_preview.png
Figure 12: Preview recent ticket data

When creating or viewing a ticket, review the Recent tickets tool to reduce the chances of creating duplicate tickets and find an opportunity to reference related tickets. Recent tickets will track data from one year prior to the current date and exclude deleted tickets.

Use the icons at the top to view recently created tickets by organization, location, user, or device. If the number of tickets exceeds the space provided, click View more tickets appears to open a new tab that is pre-filtered to the selected data.

Expand Visibility

Other functionality in the ticket editor includes the ability to expand or collapse the response or activity section and extend the WYSIWYG box.

To change the width of the section, move your cursor between the response editor and the Recent tickets section until a blue vertical line appears. Click and drag the blue line to the left or right, according to your preference.

expand visibility on ticket.png
Figure 13: Expand visibility in a ticket (click to enlarge)

To change the length of the response editor, move your cursor over the bottom right corner of the box. When the cursor changes to a double-arrow icon, click and drag the box up or down accordingly.

Additional Resources

Refer to NinjaOne Ticketing: Resource Catalog to learn more about this feature.

The following resources go further into detail regarding tools mentioned within this article: 

FAQ

Next Steps