| Info |
|---|
Available for folios and portfolios |
The Team Workload report presents the team workload by period and by titles based on the issues due dates. To access this report, click on the Report tab (or hit '6') and then click on the 'View report' button next to the Team workload report preview. This will bring up the report with the today's date as the default start (From) and end (To) date. The report will be automatically refreshed when one of its parameters changes. | Note |
|---|
| If an issue does not have a due date, FOLIO will take the end date of the folio as a fallback. |
The report first presents a bar chart showing a bar of assigned hours for each role or member grouped by period: color are automatically assigned based on the number of roles or members. Hovering the bars will open a tooltip showing the precise assigned hours. The dates labels on x-axis can be clicked to navigate to the detailed workload information for the period ending on that date. Team Workload Chart
| Lozenge | Description |
|---|
| Max. Effort | Indicates the total regular hours that the members have available based on the availabilities of their wage tables within the report''s period. |
|---|
| Assigned | Indicates the sum of the remaining estimates of the issues that are not yet earned (done) and that are assigned to the members. |
|---|
| Available | Indicates the total regular hours that was not yet assigned. It is computed by subtracting the assigned effort from the maximum effort.
A negative value indicates an overload and the lozenge will turn red. |
|---|
Issues | Indicate the total number of issues (including "at risk" and overdue issues) . |
|---|
| At Risk | Indicate the total number of issues considered "at risk".
Issues are considered ''at risk'' if their remaining estimate is greater than the time left until their due date.
Note: If at least one issue is at risk the lozenge will turn yellow.
|
|---|
| Overdue | Indicate the total number of issues considered "overdue".
Issues are considered ''overdue'' if their due date is before the report''s start date.
Note: If at least one issue is overdue the lozenge will turn red. |
|---|
Detailed period sectionDetailed information for all periods follow the chart. Each of these sections shows the list of roles, ordered alphabetically and grouped by team roles and then by team member.
| Column | Description |
|---|
| Roles | Team roles |
|---|
| Name | The full name of the member. Hovering the name will show the "JIRA user popup" 
|
|---|
| Max. Effort | Indicates the total regular hours that the members have available based on the availabilities of their wage tables within the period. |
|---|
| Assigned | Indicates the sum of the remaining estimates of the issues that are not yet earned (done) and that are assigned to the members within the period. |
|---|
| Available | Indicates the total regular hours that was not yet assigned. It is computed by subtracting the assigned effort from the maximum effort. A negative value indicates an overload.
|
|---|
| Issues | Indicate the total number of issues (including "at risk" and overdue issues) within the period.
Note: You can view the detail list of issues by clicking on the number
|
|---|
| At Risk | Indicate the total number of issues considered "at risk" within the period.
Note: You can view the detail list of issues by clicking on the number |
|---|
| Overdue | Indicate the total number of issues considered "overdue" within the period.
Note: You can view the detail list of issues by clicking on the number |
|---|
| |
|---|
| From/to | Indicate the period start and end dates. |
|---|
| Unassigned | Indicate the total remaining hours for issues that are not yet assigned to a team member. |
|---|
| Info |
|---|
Since the issue scheduling of this report is based on the due dates, the remaining estimates issues may overlap multiple periods. E.g.: Issue with a due date on January 31 with a remaining working time of 70 hours. When selecting weekly report period, the issue remaining time will be dispatched over two periods as show below: From January 19 to January 25 : 30h From January 26 to February 1st (due date period) : 40h
Note that remaining hours dispatching take into account the regular hours per days and non working days specified in Folio Configuration.
|
Issues panel
| Link | Description |
|---|
| Report parameter | Bring you back to report configuration |
|---|
| View in issue Navigator | Bring you to the JIRA issue navigator screen |
|---|
| Issue key | Clicking on the issue key bring you the JIRA Issue screen |
|---|
Configuring the reportTo change the period covered by the report, simply set the dates in the 'From' and 'To' fields to whatever dates you want. The actual period considered will span from the latest of today's date and the date entered in "From" field. You can specify which frequency the report should use to break down the overall period. For example, selecting Monthly frequency will show you workload broke down by calendar months. Select "Total" value in the Frequency to get team workload for the complete period, with no break down. You can finally limit the workload considered to a certain number of roles and/or members. Simply select/deselect the member you are interested in and the report will be instantly refreshed to reflect the new selection. Selecting or deselecting a role will cause the list of available members to be updated accordingly. See the table below for detailed information about report parameters.
Team Workload report parameters 
Team Workload report parameters details | Grouping By | - Role: bars in the chart represent team roles
- Member: bars in the chart represent team members
|
|---|
| From | Start of the timeframe for that report. The start date can be any date from today's date to any date in the future.
Note that clicking on today link set the report start date to today's date. | Note |
|---|
| If the report start date is before today, the report start date will use today's date as start date. |
|
|---|
| To | End of the timeframe for that report. Notes: - Clicking on folio end link to set the report end date to folio end date.
- There is no end date limitation as for start date, therefore issues within the Folio "scope" and with due date within the selected report end date are included
|
|---|
| Frequency | This allow you to group your team workload Weekly, 2 weeks, 4 weeks, Monthly andTotal
Note that report start date "day" will be the periods starting day. This means if your report start date is a Tuesday and the frequency is Weekly the report will display weekly expenses from Tuesday to next Monday. Monthly frequency breaks down the report data by calendar month. Total means no break down will occur: all issues for the selected period will be included in a single section. |
|---|
| Roles | Position titles to be included in the report |
|---|
| Members | Team members to be included in the report |
|---|
Printing the reportSelecting the "Printable" item in the report's action menu found at the top right of the report's parameters panel to get a printer-friendly version of the report. Printable version of the report 
| Anchor |
|---|
| ExportToExcel |
|---|
| ExportToExcel |
|---|
|
Exporting to ExcelThe Team Workload report can be exported to Excel format to give you all the latitude you need to further digest, analyze or graph the data. Do it by selecting the "Export to Excel" item in the report's action menu found at the top right of the report's parameters panel. The parameters that were used to generate the report can be found on the second tab of the generated spreadsheet Excel export of the report
|