4.3 Team Report
1. Introduction
In [Report], you can count working hours by Team.
Example of Team report:
2. Permission required
Users with permission to view team hours can query all hours of all members in the team, while other users can only view their own hours in the team.
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: Include team by default
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:
Team cannot be moved and must be ranked first
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.
Show members without hours: If a team member does not enter working hours, the member will be hidden by default. If this option is selected, the member 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 tohttps://dragonsoft.atlassian.net/wiki/spaces/GXDOCSPACE/pages/2153578755
4. There are equal working hours between teams
The statistical value at the bottom of the table is the result after deduplication
When querying the team report. If there are the same working hours between teams, a duplicate label will be displayed behind the team, and the mouse will move up to show which teams have duplicate working hours with the current team
Specifically, which user belongs to multiple teams will be displayed behind the user name, and the mouse will move up, and it will prompt "This user belongs to multiple teams and has repeated work hours"
5. Team Chart
Select "By team" to view the working hours histogram of each team according to the team dimension;
If "By team" is not selected, the first parameter in the Group By is used as the dimension to view the team's work time histogram, as shown in the following figure, the first one in the group is "User", which is equivalent to viewing the work time histogram of each user in the team.