Actor Lead Time Profile(2.7.10)

Some team members consistently resolve issues faster than others. Before jumping to conclusions, this visual also shows you how many issues each person delivered — because an actor who resolved 4 complex issues slowly tells a very different story from one who resolved 20 simple ones quickly.

Used carefully, this is a powerful input for 1:1 conversations, workload balancing, and identifying team members who may need process support or who are carrying a disproportionate share of difficult work.

What the reference line is

The dashed line is the median of the actors shown — half the people on the chart are at or below it and half are above, by construction. It answers "faster than half this team", and deliberately not "fast in absolute terms": on any team, fast or slow, about half the bars fall on each side. Read it as a way of finding the ends of your own distribution, never as a verdict on the team as a whole. The line is taken over people's accounts only, as Jira reports the account type: an account Jira returned no type for is drawn with its bar, labeled unknown, but is not part of the median.

What you can conclude

• For an actor well above the line with a high issue count, a reviewer could ask whether they are handling more complex work or need process support.
• An actor below the line with a low issue count may simply have a different type of work — compare issue types before drawing conclusions.
• A cluster of actors all near the line means delivery speed is similar across the team and not dominated by any individual.
• Because the line sits in the middle of the plotted actors by construction, the number of people either side of it tells you nothing on its own. What carries information is how far the ends sit from it, and how many issues those actors delivered.

How this chart works

Horizontal bar chart ranking each actor by their average lead time. That average is issue-weighted: a day on which an actor delivered twelve issues counts twelve times as much as a day they delivered one, so the bar reflects the work actually done rather than treating every day equally. A red dashed reference line marks the median of the actors shown. Bars at or below it are shown in blue, above in amber. Issue count is shown for each actor in the tooltip to support fair interpretation, and an abandoned count travels with each row; an actor whose closures in the window were all discards has no delivery measurement and does not appear. The chart shows the fastest 25 actors. Use the project filter to focus on specific teams.

Who an issue is credited to

Each issue counts for whoever completed the work: its assignee at the closing event. When the closing event names no assignee, the issue counts for the account that closed it. The chart does not show which of the two applied to an issue. App accounts and service-desk customers are left out whichever role they held, as the next section describes, and an assignee whose account has been erased is not "no assignee": the last section covers that case.

Apps and service-desk customers

When the account an issue is credited to is one Jira reports as an app (such as Automation for Jira) or as a service-desk customer, the issue is left out: it adds no bar and does not move the reference line, because an app account that closes issues within seconds of their creation would otherwise pull the line toward zero.

When an account has been erased

When a person's Atlassian account has been erased, MetaFrazo removes their identity from the stored events. Issues assigned to that account no longer count toward any actor's average or toward the reference line, and they are not credited to whoever closed them, so the line can move after an erasure.