Portfolio Actor Coverage(4.1.10)

When a project's recorded activity comes from two people, a reviewer could ask what happens to that work if either of them is away. This visual shows how many unique actors recorded events in each project each week, alongside the events-per-actor ratio, so you can see both projects with few active contributors and projects whose active contributors each record many events.

What you can conclude

• A project with only one or two active actors per week has its recorded activity concentrated on those people; the events show how many accounts were active, not how the project is staffed.
• An active-actor count of 0 does not sit at the low end of that same scale. It means the week recorded events but none of them carried an identifiable actor account, so it describes what the events named rather than how many people worked. Read it as a gap in actor attribution, not as an idle project — and see the section below, because the events-per-actor ratio is withheld for those weeks rather than shown as zero.
• A very high events-per-actor ratio in a specific project means many recorded events per active person. It is an average, so it does not show whether a few of them record most of the events; event counts measure Jira activity, not effort, so it is not a statement about how hard anyone is working.
• A project with several active actors and a moderate events-per-actor ratio records its activity from more people, at a moderate number of events each.

When the events-per-actor ratio is not measured

The ratio divides the number of a project-week's events that named an identifiable actor by the number of distinct actors they named. Events that named nobody are counted in the week's total but enter neither side of the ratio, so a week of unattributed activity cannot make its named contributors look busier than they were. When none of that week's events carried an identifiable actor there is no divisor, so the ratio is withheld rather than computed: no events-per-actor bar is drawn for that project or week, and its tooltip entry reads "not measured (no actor attributed this week)".

The active-actors bar for that same project-week is still drawn, at a measured 0. The two sit side by side and say different things. The count is a real reading — the week recorded events, and none of them named an actor that could be identified. The ratio is an absence — a figure that could not be formed at all. A ratio with no divisor is not a reading of zero events per actor.

Because each event names at most one actor, a measured ratio is never below 1.0, so a ratio bar resting on the floor of the axis was never a possible measurement. That is why those weeks are left blank instead. The week's total event count is unaffected; only the per-actor ratio cannot be formed. The same holds for a week whose only named actors are apps or service-desk customers: it has no person to divide by.

Both branches of the chart behave the same way — the weekly series shown when a single project is selected, and the latest-week comparison shown across all projects when none is.

How this chart works

Bar chart showing unique active actors per project per week, alongside the average events-per-actor ratio. The ratio counts only the events that named an identifiable actor, divided by the number of distinct actors they named; the week's total event count is shown beside it for context. Both figures count people's accounts as Jira reports the account type. Accounts Jira reports as apps (such as Automation for Jira) or as service-desk customers are left out, so an app account's events do not raise a project's actor count or its ratio; accounts Jira returned no type for are counted separately and shown beside the people's figure, never inside it. Select a project to see its weekly time series; leave unfiltered to compare each project's latest complete week. Use the date and project filters to focus on specific periods or teams. Where the events-per-actor ratio could not be measured, its bar is omitted rather than drawn at zero. A week in which a project's only recorded events were its own creation, change, archiving, unarchiving, trash, restore or deletion has no bars: those events describe the project rather than work in it.

With no project selected, the panel compares projects. This chart reads each project's latest complete week and does not count the week in progress. Projects report in different weeks, so the chart names no single week.

With a project selected, the panel becomes that project's weekly series instead, and the week in progress is not counted there either: the series shows complete weeks only.