Topic
This article describes the ticketing information shown in NinjaOne reports. To learn more about ticketing, refer to NinjaOne Ticketing: Getting Started. To learn more about the Report Library, refer to Getting Started with Reports in NinjaOne.
Environment
- NinjaOne Ticketing
- NinjaOne Reports
Description
The Ticketing report is a summary report that can be applied to a single organization or globally. Once created, the report can be filtered to display data for various data groups. If no group is selected, then all data for the selected date range will be applied. Results may be truncated to a maximum of 5,000 entries.
Select a topic to learn more about the filter or report section:
- Date Ranges
- Open, Pending, and Resolved Tickets
- Resolution Time
- Ticket Volume
- Technician Ticket Efficiency
- Custom Datasets for Ticketing
- Additional Resources
Date Ranges
The date range is a drop-down menu at the top of the report.

The dates and times in these reports are set to your time zone in NinjaOne. The time of the day starts at 00:00:00.000 or 12:00 A.M.
Only tickets created within the date range selected will appear in the report. For example, if you select "This Month" but all existing tickets were created over a month ago, then the report will be blank as they are out of range, regardless of what actions may have been taken on the ticket recently (for example, a ticket that was created 2 months ago and resolved yesterday will not appear on the report). You can use the Refresh icon in the top-right corner of the report page to reload the ticket information.
| Selection | Definition |
|---|---|
| This Month | The report shows this selection by default. This is the current month, so if today is February 10, the report would show data from February 1 to February 10. |
| Last Full Month | This is the most recent full month, so if today were February 10, the report would show data from the entire month of January. |
| Today | The report shows data for the current day up to the current minute. |
| Last Week | The report shows data for the last full week (Sunday to Sunday). |
| Last 7 Days | The report shows data for the last 7 days, starting with the current day. |
| Last 30 Days | The report shows data for the last 30 days, starting with the current day. |
| Last 90 Days | The report shows data for the last 90 days, starting with the current day. This option is only available for reports targeted to organizations. |
| Custom | The report shows data for a manually selected date range. This option is only available for reports targeted to organizations. |
Open, Pending, and Resolved Tickets
- Open tickets are defined as tickets created within the selected date range that currently have the status Open (either the default or a custom status).
- Pending tickets are defined as tickets created within the selected date range that currently have a status of Waiting (either default or custom status).
- Resolved tickets are defined as tickets created within the selected date range that currently have a status of Resolved or Closed (whether the default or a custom status).
Resolution Time
- Mean Time to Resolve: Using the tickets that are currently Resolved/Closed, is the average of the time it takes to resolve them. The time it takes to resolve a ticket is calculated from the time it was created to the last time it was moved to a Resolved status.
- If a ticket is resolved and then reopened, it is not counted for this field.
- If a ticket was resolved, reopened, and then resolved again, the field calculates the time between reopening and the final resolution.
- One Touch Resolution: For each ticket that is currently Resolved or Closed, the number of public comments made by a technician on the ticket is counted. Then NinjaOne calculates the percentage of users with at most one comment.
- Comments from contacts, end users, requesters, or similar parties are not included in the calculation.
- Private comments are not calculated.
- If there are four (4) tickets total, and 3 of them have one comment or fewer, then the resolution percentage will be 75% (3/4).
- First Response Time: Using tickets that have at least one public comment, the average time elapsed between the ticket’s creation and the time of the first public comment.
- If there are no public comments on the tickets, the count will show 0 seconds.
- Private comments are not calculated.
- All public comments, including those from automations, are included in the calculation.

Tickets/Resolution Time
Using the tickets that are currently Resolved/Closed, and the time it takes to resolve them, as in Mean Time To Resolve. Percentages are calculated for each defined range using this resolution time.

Technician Touches
Using the tickets that are currently Resolved/Closed, and the count of public tech comments, as in One Touch Resolution. Percentages are calculated for each defined range using these counts. The numbers indicate how many public comments the technician made on a single ticket (for example, three to five indicates tickets with a minimum of three and a maximum of five public comments).
The calculation accounts for all public technician comments and does not distinguish whether the same or different technicians made them.

Ticket Volume
Total
This section groups tickets created within the selected time range by their current status. The total number of tickets created within the selected time range is listed at the bottom.
The percentage for reopened tickets accounts for tickets that had a Closed or Resolved status and were later changed to an open/pending/waiting status; this can include tickets that were resolved, reopened, and closed again. If a ticket was resolved and reopened multiple times, it would count only once. The calculation is per ticket, not per reopening.

Tickets Created per Day
This section displays tickets created within the selected time range, showing the specific day of the week they were created.
Tickets Created per Hour
This section shows a more specific time of day that the ticket was created within the selected time range. The calculation accounts for every three hours, starting and ending at midnight per your configured time zone.
Technician Ticket Efficiency
Tickets Taken
This section lists all technicians assigned to a ticket created within the selected date range. The calculation accounts for each technician assignment within the same ticket.
Tickets Solved
This section accounts for tickets in the Resolved status only.
In Tickets Solved, the technician who set the status to Resolved is listed, regardless of who was assigned to the ticket. For example, if ticket #1094 was assigned to Technician A, but Technician B changed the status, then the report lists the ticket under Technician B.
Custom Datasets for Ticketing
You can add custom data tables to any report. Refer to NinjaOne Reporting: Custom Data Tables for Summary Reports for more information. The custom data tables include the following information for NinjaOne Ticketing:
Ticketing - All Tickets
View a comprehensive top-level table of ticket information, representative of ticket board data. Filter the tickets and choose which data columns to include in the report before adding this custom data table.

Ticketing - SLA Compliance Summary
View a pre-configured table of SLA compliance information that demonstrates adherence to the Service Level Agreements of the organizations being reported on. Filter the tickets and choose which data columns to include in the report before adding this custom data table.
You can aggregate the data to group the information by organization or SLA profile. If you choose not to aggregate the data, the SLA profile and the Organization will populate as column headers.

Ticketing - SLA Breach Detail
View a list of every SLA breach in the reporting period, with one row for each ticket. The table sorts the breaches by the largest overage first, so you can identify the most serious SLA breaches.

Ticketing - SLA Average Response Time by Priority
View the average first response time for each priority, compared against the SLA target. Use this table to review SLA performance by priority.

Additional Resources
To learn more about NinjaOne Ticketing, refer to Ticketing: Resource Catalog. For further details about NinjaOne Reporting, refer to Reporting: Resource Catalog.