Worklog Effort Distribution per Actor(4.5.9)

Worklog data provides the most direct measure of effort — the hours that team members have explicitly recorded against issues. This visual shows total and average weekly hours logged per actor, making workload distribution visible in a way that event counts alone cannot.

What you can conclude

• Actors consistently logging significantly more hours than the team average raise a question about how work is assigned; the hours show what was recorded, not how sustainable it is.
• Actors with very low worklog hours relative to their event count may not be logging time consistently — either a data quality issue or a process adherence gap.
• A balanced worklog distribution means logged hours are spread evenly across the actors who log time.

How this chart works

Horizontal bar chart showing total and average weekly hours logged per actor from worklog time data. Each actor is labeled with the type Jira reports for the worklog's author: a person, an app such as Automation for Jira, a service-desk customer, or unknown when Jira returned no type. Use the date, project, and actor filters to focus on specific teams or periods.

The total covers every week in the selected range, including the week in progress, because hours logged in a part-week were really logged. The weekly average covers complete weeks only, because a rate over an unfinished week is not comparable to one over a finished week. This chart ranks actors rather than weeks, so the week in progress has no bar of its own.

Hours whose author cannot be identified are left out of this chart, including hours logged by a person whose Atlassian account has been erased; they are never credited to whoever last edited the worklog. The Weekly Effort Trend visual keeps those hours in its weekly totals.