Service request reports let you compare request counts, processing delays, recorded hours and the mean time between failures for Spots. The reports use different data and time bases. Selecting the same period therefore does not include the same service requests in every report.

Open a report and select the comparison filters

From the browser's main menu, open Dashboard → Report pages and select a page using the name selector at the top. An administrator can open the Add new report selection at the top of the page, search for a report by name and drag it onto the page. The basic version of Report pages provides one page, with each report appearing once. Additional features allow multiple pages and the same report with different filters.

Open Settings in the report's title bar. In the settings panel, All filters contains the data filters, Group by contains the breakdown options, and Report settings includes options such as Chart type. In the settings row, Tme period for the data selects the data period, and Time grouping for data selects, for example, monthly or yearly results. MTBF has no time grouping.

Select the period before comparing figures. The initial settings for a new report vary:

  • The turnaround time, hours and on hold reason reports use a calendar period from the start of the previous year to the end of the current year.
  • MTBF and the count report by Spot use the current calendar year.
  • The status, count, processing delay and commenting delay reports initially use a date range with no limits filled in. In this case, the data starts with the first service request.

A saved report has its own settings. When specifying a date range, fill in both the start and end dates to trigger a new search. Time limits follow your user account's time zone; the default is Helsinki.

Report-specific filters can restrict, for example, folders, Spots, service request categories, user roles, customers and priorities. Values within the same standard multiple-selection filter are alternatives, while the conditions in different filters must all be met. A folder filter includes subfolders and requires a Spot linked to the request. The same filters are not available in every report: for example, a status filter is available in the status and count reports, but not in the delay or MTBF reports.

In reports where Additional fields is available, all specified field conditions must be met. Text searches are case-insensitive, and number searches look for the specified number as part of a string. A number search therefore does not set a minimum or maximum value. A date field condition checks whether the field is empty or filled in.

The data is restricted by your access rights. Another user opening a report with the same name may see different data. A saved filter hidden from you may still restrict the result; the view notifies you of such filters. An administrator saves the page's reports and filters using Control report page → Save the page at the top of the page. Saving changes the shared page configuration, but does not save its figures as a fixed snapshot.

If needed, see adding a report and using time periods and filters.

Three count reports

  • Service requests by status separates the current statuses Open, In progress, On hold and Completed. You can break down the results by user role or priority.
  • Number of Service Request by Spots shows counts for each Spot. Requests without a Spot may appear as an unknown group.
  • Number of Service Requests shows the total count. You can break it down by user role, priority, service request category, Spot or service request field.

These reports first filter requests to the selected period based on their creation time. A request currently marked Completed is then counted in the chart's time group based on its completion time. Open, In progress and On hold requests are counted by creation time. Cancelled and Forwarded requests are excluded even if you select them in the status filter.

For example, a request created on 31 January and completed on 2 February does not appear in a count report restricted to February, because its creation time falls outside the filter. When the data period covers January and February, the request appears among February's completed requests. If completion falls outside the chart's time groups, the request may be omitted from the chart.

The status breakdown shows requests' current statuses, rather than their statuses at the end of each past month. Changing statuses can therefore also change results for earlier time groups. The figures are request counts; they do not calculate percentages or use a denominator.

Counts by additional field value

In the count report's Group by section, select By service request field, then choose the desired field from Select field. No breakdown is produced until you select a field.

Only requests that have the selected field are counted. An existing but empty field belongs to the Others group; a field that is entirely absent is excluded. In the current calculation, the No value of a yes/no field also goes into the Others group. The breakdown total may therefore differ from the same report's ungrouped total.

Long values are shortened, and values containing special characters may merge into the same group. For comparisons, use short, clearly distinct field values and check unclear groups against the original requests.

Three delay reports

Delay reports filter and group requests by creation time. The required processing event may occur after the selected creation period. You can break down all three reports by service request category, user role or priority.

ReportIncluded requests and measured time
Service request turnaround timeRequests currently marked Completed: the time from creation to the recorded completion time.
Service request processing delayRequests with a recorded processing start time: the time from creation to the first recorded start time. The current status does not restrict the data.
Commenting Delay of Service RequestsRequests with at least one comment: the time from creation to the earliest comment. The current status does not restrict the data.

The result for each time group and breakdown group is the sum of the individual request durations divided by the number of included requests. A missing start time or comment does not mean zero delay; the request is excluded from that average. One day and three days give an average of 2.00 days for two requests.

The calculation uses actual elapsed time, with a day equal to 24 hours, and rounds the average to two decimal places. Weekends, nights and time On hold are not deducted. These figures are not recorded work hours. Any negative durations for individual requests in the processing and commenting delay reports are treated as zero.

Turnaround time and processing delay may also appear in d h min format. This display is converted from the day value already rounded to two decimal places, so it does not increase measurement precision. Commenting delay is shown in days.

How do statuses and comments affect delays?

A request cannot move from Completed, Cancelled or Forwarded to another status. A completed request therefore cannot be reopened and completed again to change its turnaround time. The completion time is saved to the service when the request is marked completed.

The processing start time is recorded during an explicit transition to In progress, if no earlier start time exists. An already recorded time is retained through subsequent permitted status changes. However, the In progress status alone does not guarantee a start time: an automatic transition caused by assigning a responsible role may lack a timestamp. Such a request is missing from the processing delay report. Taking a request into processing on mobile is also recorded on the server; a time entered separately on the phone is not used as the start time.

Commenting delay is based on the earliest remaining comment. Deleting the first comment may cause the next comment to become the basis for the calculation. If all comments are deleted, the request is excluded from commenting delay.

An empty delay group does not mean a delay of zero days. A group missing from grouped data has no value. Without a breakdown, the calculation does not handle an empty time group safely, so generating the report may fail. Try a longer period or a breakdown if a delay report does not load.

Service request recorded hours

The hours report uses ended entries linked to an existing service request, with service request as their entry type, whose time interval overlaps the selected period. Ongoing entries are excluded. The request's creation time or current status does not in itself exclude an entry.

Without a breakdown, the report totals only the portion of the time between each entry's start and end times that falls within the time group being examined. The total is converted to hours and rounded to two decimal places. For example, an entry from 23:00 to 01:00 contributes one hour to the following day's report.

You can break down hours by service request category, folder, Spot, user role or priority. A breakdown changes the calculation: entries entirely within a time group use their saved minutes. Entries crossing the start or end boundary use the portion calculated from their start and end times. The saved number of minutes is rounded up to a full minute when the entry is saved. In a breakdown, minute totals and portions crossing a boundary are converted to hours and rounded to two decimal places before being combined. The sum of the breakdowns may therefore differ from the ungrouped result.

The breakdown is based on the service request's details. A user role breakdown is not a report of entries by individual people. Recorded hours and piece counts is a separate report: it separates hours and pieces, provides entry-specific filters and also includes ongoing timing. The service request hours report does not separate pieces into their own result or provide an approval filter. Use the general entry report when you need to examine data by the person who recorded it, approval or unit type. See also viewing hours and costs.

Mean time between failures (MTBF)

In All filters, set Palvelupyyntölaji to the category used for fault reports, and select the required Spots or folders. Without a category filter, all of the Spot's service requests matching the filters are counted as events. The calculation does not identify physical failures or restrict requests to Completed: Open, In progress, On hold, Cancelled and Forwarded requests may also be included.

A Spot's value is calculated as the duration of the selected period in days ÷ the number of service requests created during that period that match the filters. It is not the average difference between consecutive failure timestamps or the device's measured operating time. A period of approximately 30 days and three requests produces 10.0 days. Extending the period can change the value even without additional requests.

Only Spots with at least two requests matching the filters are included. Requests without a Spot are excluded. The value is rounded to one decimal place. The Spot comparison shows up to 45 Spots in descending order of request count; ties are ordered by Spot name. Filter the data to see the Spots you want.

Select Group by → By folder for a folder comparison. In the Folder selection that appears, you can select the folders to compare; their subfolders are combined with them. Without a separate folder selection, the breakdown uses the Spots' own folders.

A folder's value is the unweighted average of the unrounded MTBF values of Spots with at least two requests, rounded to one decimal place. It is not the period's duration divided by all requests in the folder. For example, over a 30-day period, Spots with two and three requests have values of 15 and 10 days; the folder result is 12.5 days. If a selected folder has no qualifying Spots, its result is 0. This zero does not indicate a measured mean time between failures of zero days.

For MTBF, Report settings → Chart type offers stacked columns or horizontal stacked bars. A single value represents the entire selected period.

The reason for the on hold status

The report counts requests by reason, rather than waiting days or the total number of transitions to On hold. Each request is assigned to the time group containing its creation time. The report may include requests currently On hold and requests in another status whose status history includes On hold. The current status therefore does not have to be On hold.

The history includes status changes recorded during that time group where On hold appears as either the old or new status. The request's creation time must also fall within the same time group. A February On hold event for a request created in January therefore does not, on its own, count towards February's reasons.

A request is counted under at most one reason within a time group. For a request currently On hold, its current reason takes precedence over historical reasons. For a request in another status, the last processed reason in its history is selected, but the history records are not sorted by timestamp. When there are multiple historical reasons, the report's reason therefore cannot reliably be considered the most recent one chronologically. A missing reason for a request currently On hold may also prevent the report from being generated.

How cancellation and deletion affect reports

Cancellation retains the service request's details but removes it from the three count reports. A cancelled request may still be included in processing delay if it has a recorded start time, and in commenting delay if it has a comment. A cancelled request linked to a Spot may also be included in the MTBF calculation. An ended time entry may still appear in the hours report. A cancelled request is excluded from turnaround time because that report requires the Completed status.

A permanently deleted request is absent from service request reports. Its entries are also excluded from the hours report described in this article, even if an entry survives deletion: the report requires a link to an existing service request. Cancellation and deletion therefore have different effects on reports. For the conditions for these actions and how data is retained, see cancelling and deleting a service request.

Check the results before comparing

From the browser's main menu, open Manage tasks → Service requests → Service requests. In the shorter menu, the path is Manage tasks → Service requests. On the page, select Datatables → Default view. Find a few requests you know and compare them with the report using the same time limits and filters. Also check the table's own filters so they do not hide requests needed for the comparison.

Check the request's current status and the Created and Completed at columns. If a column is missing, open the column selector using the columns icon in the table header. To check delays, use Duration: Created -> Completed, Duration: Created -> In progress and Duration: Created -> First comment. These show individual request durations, rather than directly showing the report's average rounded in days. An empty processing duration may be due to a missing start time, even if the current status is In progress.

Open a request using the pencil icon on its table row. In the edit window's Comments tab, you can check comments and their times. In the Logged work hours tab, check the start, end and duration of the entry you are comparing with the hours report. For MTBF, count the Spot's requests matching the filters and verify the full duration of the selected period.

The data viewed in the browser also includes service request changes, comments and entries saved to the service from Android and iOS. An entry made on mobile appears in this hours report only after it has been ended and saved to the service. Refresh the report after saving changes.

If you use Report settings → Show average value, the additional value is the arithmetic mean of the included series values at the same time point. A missing value entering this calculation is treated as zero. This option does not calculate a combined average for all requests in a delay report weighted by request counts. The average of averages for groups of different sizes may therefore differ from the ungrouped delay report's result.

Report filters and display options do not change service requests or their history. However, changes to requests' statuses, comments, additional fields and Spot links can change results for past periods too. After saving, reload the report page and verify that the selected period, breakdown and filters were retained. If the result is empty or the report does not load, see troubleshooting an empty report.