Summary

Introduce a Workload Balance Report to visualize how work is distributed among team members. The report helps identify overloaded or underutilized members and maintain a balanced assignment of tickets.

Goals / Why

• Improve resource allocation and reduce bottlenecks.
• Ensure fair workload distribution across team members.
• Provide visibility for managers to rebalance work proactively.

Scope (v1)

• Filters: Project (required), Iteration (optional), Status, Priority, Label, Assignee (multi-select), and Date Range.
• Metrics:
  • Number of tickets assigned per user.
  • Ticket load by priority (stacked breakdown).
  • Optional: total estimated effort or story points (if enabled in project).
• Display:
  • Bar or heatmap chart showing tickets per user.
  • KPI cards: total open tickets, average per user, top overloaded member.
  • Table view with each user’s open/closed counts, average ticket age, and overdue count.
• Export: CSV of current view.
• Respect tenant and project permissions.

Non-Goals (v1)

• Automatic workload rebalancing or ticket reassignment.
• Effort forecasting or productivity scoring.

Acceptance Criteria

• Chart displays ticket count per assignee (grouped by priority if selected).
• KPIs correctly reflect totals and averages.
• Filters work for project, iteration, and date range.
• CSV export includes all visible data columns