Task reports answer different questions: how many tasks there are, what their statuses are, whether they are completed on time, and how much time has been allocated to or recorded against them. The same time period does not select the same data in every report.
Open a report and check the filters
In the browser’s main menu, open Dashboard → Report pages. Select a report page from the name selector at the top. If the report you need is missing, an administrator can open Add new report at the top, drag the report onto the page and select Save the page. See adding and arranging reports.
Open Settings in the report’s title bar. In the right-hand panel, All filters limits the data, Group by divides it into additional groups, and Report settings changes how it is displayed. Above the chart, Tme period for the data sets the period covered by the data, and Time grouping for data divides the figures into days, weeks, months or years. The default grouping is monthly. Year view cannot be combined with daily grouping.
The default period for a new Hours allocated to tasks report covers the current calendar month and the next five months. For the other task reports discussed here, the default period covers the previous and current calendar years. A saved report may have different settings.
A relative period changes over time. A calendar-based period starts from the full current week, month or year; a period calculated from today starts from today’s date. Use fixed start and end dates when you want to repeat a comparison. The following data selection rules apply when the view is limited by dates. Empty date selections should not be treated as the same filter. See time periods and filters.
The report uses the data your permissions allow you to access. An administrator may see more information than a regular user. Conditions in different filter fields apply together: grouping does not restore data excluded by filters or permissions.
Task counts and current statuses
- Completed vs. other Tasks shows a series for completed tasks and a combined total for all other statuses.
- Tasks by status shows the series Planning, Open, Overdue, In Progress, In Review and Completed.
- Number of Tasks shows the total count. Of these six task reports, only this one offers a status filter under All filters and the By status option under Group by.
These three count reports first select tasks whose due date falls within the data period and which have no completion date, or whose completion date falls within the period. On Hold tasks are excluded. If a completion date exists but falls outside the selected period, a due date within the period alone does not include the task. Missing dates can also exclude a task.
After this initial selection, the figures are assigned to time groups as follows:
- Completed vs. other Tasks and Tasks by status count a task with a completion date in the completed series based on its completion date, regardless of its current status. Other statuses are counted based on the due date. An unfinished task whose due date and completion date fall in the same time group can therefore appear in both the completed and unfinished series.
- Number of Tasks counts tasks currently marked Completed based on their completion date, and other tasks based on their due date. An unfinished task’s completion date still affects the initial selection described above.
The reports do not show what a task’s status was at the end of a past day. They use current information. For example, an open task due on 31 January appears among January’s other tasks. When it is completed on 2 February and its completion date is recorded as 2 February, it moves to February’s completed tasks. If the report is limited to January, the task is removed from its data.
Correcting a task’s status, due date, completion date, responsibility or priority can change figures for earlier periods. If a task is returned to an unfinished status and its completion date remains, check both dates and the current status before comparing reports.
Limitations of grouping in count reports
Under Group by, By priority divides tasks by priority. By responsible role uses responsible roles, rather than the people who completed the tasks.
In Completed vs. other Tasks and Number of Tasks, the task’s own responsible role takes precedence; if it has none, the responsible roles linked to the task are used. In Tasks by status, a linked responsible role takes precedence. A task assigned to a person without a responsible role may be excluded from role groups. A task linked to several roles may appear in several groups.
Number of Tasks also has the following limitations:
- By priority: the count of other tasks at the same priority replaces the completed count if both exist. For example, three completed and two open tasks with the same priority in the same time group may produce a count of two instead of five.
- By responsible role: tasks counted through the task’s own responsible role may replace tasks counted through responsible roles linked to that same role. The figure then does not include the sum of both sets.
- By status: Planning does not appear as a series, although planning tasks may be included in the report’s ungrouped total.
Check the total without additional grouping. The sum of role groups may not equal the number of unique tasks in any case.
Weekly grouping has a separate date limitation. When role, priority or, where available, status grouping is added to a count report, the last day of the week is not included through to the end of the day in the same way as it is without additional grouping. A completion date with a time on the last day of the week may therefore be excluded from the grouped count. Check such differences using a fixed period, daily grouping and no additional grouping.
On-time completed tasks
On-time completed tasks shows the percentages of tasks completed on time and late. It includes only tasks currently marked Completed that have a completion date and whose due date falls within the data period. The time group is also determined by the due date. The completion date does not have to fall within the same reporting period.
The on-time percentage is the number completed on time divided by the total number of included completed tasks, multiplied by one hundred. The late percentage is calculated in the same way. Unfinished and on-hold tasks are excluded from the denominator, even if their due dates have passed.
The local day of the completion date is compared with the due date in the user’s time zone: a task completed on its due date counts as completed on time. Percentages are rounded to two decimal places. If no tasks are included, both percentages are zero.
For example, three tasks completed on time and one completed late produce percentages of 75% and 25%. Two unfinished tasks in the period do not change these percentages.
With By responsible role and By priority grouping, percentages are calculated separately from each group’s own data. For role grouping, a responsible role linked to the task takes precedence over the task’s own responsible role. A task linked to several roles may affect the percentages in several groups. Do not add or average the groups’ percentages to obtain a percentage for the full dataset.
Hours allocated to tasks
Hours allocated to tasks is based on allocation start and end times. The task’s due date, planned duration, the allocation’s separately saved total minutes and actual time entries do not determine the figure. The task needs an allocation with start and end times. See allocating resources in the Gantt view.
The data selection includes tasks whose allocations fall within or extend across the data period. For each selected task, the portions of its allocations falling within each time group are counted. Overlapping allocations are added together. For example, two separate two-hour allocations for the same task produce four allocated hours, even if they occur at the same time. The figure does not represent equipment running time or the total elapsed duration of the work.
Allocation minutes are added up for each task and converted into hours. Each task’s hours are rounded to two decimal places before being added together by status or group. This may cause small rounding differences between totals calculated using different time groupings.
The visible statuses are Planning, Open, Overdue and In Progress. Completed, In Review and On Hold do not appear as series. Moving a task to one of these statuses can reduce the visible allocated hours even if the allocation remains. The report is therefore not a total of allocated hours across all statuses.
By priority divides the hours for visible statuses by the task’s current priority. By responsible role uses only the task’s own responsible role. Hours for a task assigned only through linked responsible roles may therefore be missing from role grouping. Check a missing figure without additional grouping and compare it with the allocation times and the task’s current status.
Task recorded hours
Task recorded hours uses task time entries linked to a task. General working time entries and service request entries are not part of the same dataset. When the view is limited by dates, an entry needs both a start and an end time: an ongoing entry does not accumulate continuously updated hours in this report. The task does not need to be completed for the entry to be included.
For entries entirely within a time group, the saved minutes are used. When the start or end time changes, the duration saved is calculated from the difference between the times and rounded up to whole minutes. For example, a fully included 90-minute entry produces 1.50 hours. Overlapping task time entries are also added together; overlapping time is not deducted.
For an included entry that crosses a time group boundary, the portion within the group is calculated from the difference between the start and end times. This portion does not use the saved minutes. Without additional grouping, the total hours for fully included entries are rounded to two decimal places, the portions crossing boundaries are added, and the result is rounded again to two decimal places.
Data selection has limitations. An entry spanning the entire selected period may be excluded. The end boundary uses the end date itself, rather than the end of that day, and comparisons are strict. Entries exactly on a boundary or starting during the last day may therefore also be missing. These boundaries should not be assumed to correspond to midnight in the user’s local time zone. Check entries on boundary dates in the source data and, if necessary, compare them using a wider data period with daily grouping.
In this report, despite its name, By responsible role groups entries by the user who made the entry. A responsibility filter specifying a person also applies to the entry’s user. However, the responsibility filter also requires responsibility records to exist for the task, so an entry may be excluded if the task has none. A responsibility filter specifying a role uses the task’s responsibility assignments. By priority uses the task’s current priority.
When grouping by user, the minutes of fully included entries are added up and converted into rounded hours for each user; portions crossing boundaries are rounded per entry before being added. When grouping by priority, fully included entries are also rounded per entry. The sum of the groups may therefore differ from the ungrouped total hours.
The Completed by filter under All filters does not reliably filter entries by the person who completed the task in this hours report. Check the result without it. A task belonging to several selected categories may also cause its entries to be counted multiple times when filtering by category. Category filters may also multiply task counts in count reports; verify an unexpected total without the category filter.
Recorded hours and piece counts is a separate report. It offers filters such as approval, entry type and unit, which the task hours report does not offer. The task hours report is not a summary of approved working time or piece counts. See choosing a report type.
Account for partial periods and time zones in hours reports
The overall data period and the calculation boundaries of an individual time group are different things. Monthly and yearly groups cover full calendar months and years, even if the selected data period starts or ends partway through them.
Hours reports clip time to the time group’s boundaries, but do not then clip it separately to the overall data period. A bar for a partial month or year at either end may therefore include time outside the selected dates. For recorded hours, this applies to an entry that passed the initial selection. For allocated hours, other allocations for the selected task within the same time group may also affect the figure.
When you need hours for specific dates, use a fixed period and daily grouping, and compare the results with the saved allocation or entry times. Simply adding up monthly bars does not verify the hours for a partial month.
The report uses the user’s time zone setting; if no setting is available, it defaults to Helsinki. However, the selection of hours data and the calculation of time portions handle time zones differently. A shared time zone setting or daily grouping therefore does not guarantee consistent boundaries for all hours. In particular, check entries near day boundaries directly in the source data.
Verify the result and save the view
- Select fixed start and end dates and begin without additional grouping. Check the time grouping and any previously saved filters.
- Compare the count report with a few known tasks: check their current status, due date, completion date and responsible roles.
- Compare allocated hours with allocations, and recorded hours with ended task time entries. Account for overlaps, period boundaries, visible statuses and rounding.
- Add filters and grouping one at a time. If the result changes unexpectedly, compare it with the original view and the limitations described above.
Changes made on Android and iOS affect the report’s data once they have been saved to the service. When task timing is stopped on Android, the end time is saved using the time at which the server processes the stop. When editing an entry on iOS, the times entered are interpreted in the device’s time zone and sent to the service as UTC times. Check the information saved to the service; the elapsed time shown on the phone alone does not verify the duration used in the report. Permissions and locks for correcting entries are described in correcting a time entry.
Changing settings changes the view, rather than the tasks, allocations or entries. An administrator saves an existing report’s permanent settings using Save Settings in the title bar, which is visible while settings are open. To save a new report, use the Save the page button at the top of the page or Control report page → Save the page.
Wait for the success notification, reload the page and check that the period, filters and grouping have been retained. Saving preserves the report’s configuration, rather than an unchanging historical snapshot of its figures. Changes to tasks, responsibilities, priorities, allocations and entries can also change results for earlier periods.