3.3.1.1 Work report

Owned by huwenhua
Last updated: Sept 13, 2023
4 min read

1. Introduction

Work reports support multi-condition and multi-angle statistics of working hours.

Example of work report:

2. Permission required

Users with permission to view project hours can query all hours in the corresponding project, while other users can only view their own hours in the project.

3. Function

3.1 Query

Support the query of date, project, user/group, and issue type. Click "More" to support: Epic, version and other system fields, custom select list fields (single/multiple choice), TimeWise extended fields of work type, and approval status.

At the same time, Filter query is supported

3.2 Group by

(1) Initial grouping structure: user>>project>>issue

You can drag the grouping conditions from the optional list on the right to the selected list on the left, and click "Apply" to take effect.

Note that the order of grouping conditions must follow the rules below:

  • Project must be above the Version/Component

  • Issue must be ranked last (except for User)

(2) When you select a custom field as the grouping condition in the global configuration, you can freely combine it with other conditions in Group by.

3.3 Column

Define the dimension displayed in the column, support system fields such as project, user, version, custom select list fields (single/multiple choice), TimeWise extended fields of work type, approval status and normal/overtime/leave hours.

3.4 Display All / Log / Plan

You can query logs or plans, or both.

3.5 More conditions

  • Show column with no data: If there is no data in a column, the column is hidden by default. If this option is selected, the column will be displayed.

  • Hide subtask and move its hours to its parent task: When selected, the subtask will be hidden and the working hours of the subtask will be recorded on the parent task.

3.6 Colum Sorting

When there is only one condition in "Group by", click the column header to sort in ascending or descending order:

3.7 Column Merge

Drag the column header to the column header to be merged to complete the merge.

Double-click the merged title to restore

3.8 Extended settings

For more details, please refer tohttps://dragonsoft.atlassian.net/wiki/spaces/GXDOCSPACE/pages/2153546016

3.9 Share report

For more details, please refer tohttps://dragonsoft.atlassian.net/wiki/spaces/GXDOCSPACE/pages/2153578728

3.10 Send and Scheduled send report

For more details, please refer tohttps://dragonsoft.atlassian.net/wiki/spaces/GXDOCSPACE/pages/2153775224

3.11 Export report

For more details, please refer to

4. Chart

  • Default: each column of data is displayed separately, as shown in the figure below:

  • Stacked: Each column of data is merged into one column, as shown in the following figure:

Log or plan can be selected in the chart view, but not both:

Click the icon of the column to hide it.

5. Query optimization in the case of big data（Quarterly, Annual）

When the total logs or plans data volume is greater than "60,000" or more, the big data thread will be enabled to query and load data in pages, with a default of 1000 entries per page.

If three users have already started big data queries at the same time, and then the fourth or more user are conducting big data queries, they will be restricted and prompted:

Note: Regular queries will not be restricted.