Use cases for Workload report
- 1 Use cases
- 1.1 Use Case 1: Individual Workload Overview
- 1.1.1 Building the report
- 1.1.2 Report example
- 1.2 Use Case 2: Priority-Based Workload Distribution
- 1.2.1 Building the report
- 1.2.2 Report example
- 1.3 Use case 3: Due Date Workload Distribution
- 1.3.1 Building the report
- 1.3.2 Report example
- 1.4 Use Case 4: Label-Based Issue Tracking
- 1.4.1 Building the report
- 1.4.2 Report example
- 1.5 Use case 5: Project Component Workload
- 1.5.1 Building the report
- 1.5.2 Report example
- 1.6 Use case 6: Workload by Status
- 1.6.1 Building the report
- 1.6.2 Report example
- 1.1 Use Case 1: Individual Workload Overview
Use cases
The Workload report is not limited to the classic view in the pivot table form for checking the number of issues on a person, the remaining and original estimation. Below we will look at many more examples of constructing a workload report besides the classic one, and also consider in which cases they would be useful
Use Case 1: Individual Workload Overview
This use case is the most popular and it provides project managers with a clear view of how workload is distributed among team members. It helps identify potential overloading of individual team members and allows for better resource allocation. For team members working across multiple projects, this report helps in understanding their overall workload. It ensures that resources are not overcommitted and helps in balancing tasks across different projects for better efficiency.
Building the report
To build this report, please select Pivot table as a chart.
In Set data please select Assignee as a row by clicking on “+ Add a field”.
Under Measures, select Count of Issues, Sum of Original estimate, Sum of Remaining estimate by clicking “+ Add a field“ and selecting measure from the list.
If you want to see additional distribution of estimated and remaining time by project or even by individual issue, feel free to select an additional row and drag and drop it using 6 dots icon to change hierarchy of data representation.
Report example
Use Case 2: Priority-Based Workload Distribution
This report provides insights into how work is distributed based on priority levels. It helps ensure that high-priority tasks are adequately resourced and that no team member is overwhelmed with critical issues.
Building the report
To build this report, please select Pivot table as a chart.
In Set data please select Assignee as a row by clicking on “+ Add a field”. Please repeat the action to add Priority row.
Under Measures, select Count of Issues by clicking “+ Add a field“ and selecting mesaure from the list.
Report example
Use case 3: Due Date Workload Distribution
This report provides insights into how work is distributed based on Due date. It helps ensure that tasks are adequately resourced and that no team member is overwhelmed with issues that should be done as fast as possible.
Building the report
To build this report, please select Pivot table as a chart.
In the Set Data section, select Assignee in the row by clicking “+ Add a field”. Repeat this step to add Due date row and select a filter for this field. For example, you can select the current month or current week to filter by upcoming dates. Expand added dimention, click on Filter field and select a filter.
Under Measures, select Count of Issues by clicking “+ Add a field“ and selecting measure from the list.
Report example
Use Case 4: Label-Based Issue Tracking
Product managers can use this report to track issues associated with specific labels, which might indicate features, modules, or specific concerns. This helps in monitoring the progress and resource allocation for particular aspects of the project.
Building the report
To build this report, please select Pivot table as a chart.
In the Set Data section, select Project in the row by clicking “+ Add a field”. Repeat this step to add Labels row.
Under Measures, select Count of Issues, Sum of Original estimation, Sum of Remaining estimation by clicking “+ Add a field“ and selecting mesaure from the list.
Report example
Use case 5: Project Component Workload
Development leads can use this report to analyze the workload associated with different components of a project, helping allocate resources where needed most.
Building the report
To build this report, please select Pivot table as a chart.
In the Set Data section, select Components in the row by clicking “+ Add a field”.
Under Measures, select Count of Issues, Sum of Original estimation, Sum of Remaining estimation by clicking “+ Add a field“ and selecting mesaure from the list.
Report example
Use case 6: Workload by Status
This report provides insights into the current status of tasks assigned to each team member, helping to identify bottlenecks and ensure timely progress.
Building the report
To build this report, please select Pivot table as a chart.
In the Set Data section, select Assignee in the row by clicking “+ Add a field”. In column select Status
Under Measures, select Count of Issues, Sum of Original estimation, Sum of Remaining estimation by clicking “+ Add a field“ and selecting measure from the list.
Report example