Disclosure: Snapbytes is the developer of SnapMetrics.
Issue count is only one view of workload
Two people can each own five open Jira issues and still have very different operating loads. One person may be working through five small requests; another may be spending most of the week on one complex item while four smaller tasks sit behind it.
Ticket count is visible, but it is not always explanatory.
Time by Assignees adds a second lens
SnapMetrics’ Time by Assignees report visualizes and compares how time is distributed across team members. Used carefully, this helps a lead understand whether work is clustering around a subset of the team or whether the apparent balance in issue counts is hiding a very different time pattern.
The goal is not to rank people. Time data needs context: issue complexity, specialization, interruptions, support duties, and part-time schedules can all change what the chart means.
Ask operational questions, not productivity questions
A healthier question is “Where is our delivery capacity being consumed?” rather than “Who is fastest?”
For example, if one specialist consistently carries far more in-progress time, that may indicate a skills bottleneck or a routing problem. If another team member has low active time but a high issue count, the queue may contain blocked or waiting work that needs a different report to explain it.
Combine the signal with the work itself
Time by Assignees becomes most useful when paired with the actual issue context. Review the outliers, look at the work types, and ask the team what the chart is reflecting.
Analytics should shorten the path to a better question. It should not replace the conversation with a leaderboard.
If issue counts make your Jira workload look balanced while the team experience says otherwise, explore SnapMetrics on Atlassian Marketplace and compare the same queue through Time by Assignees.
