Jira story points by assignee, priority or status
Checked against Atlassian’s documentation and JRACLOUD-62109 on 13 October 2026.
You want story points added up per assignee: how many points each person’s epics hold, how many are done, and the same by priority or by status. In the Atlassian Community it reads “Unable to get assignee wise cumulative story points in native dashboard”. This page says what Jira does by itself, an export that gets the numbers today, then what Sumline does.
What Jira does by itself
- Gadgets count work items; they do not add story points. A Pie Chart or a Two Dimensional Filter Statistics gadget splits a filter by assignee, priority or status and counts the work items in each. Adding up story points there is a suggestion open since 2011, with 853 votes on 13 October 2026 (JRACLOUD-62109, “Gathering Interest”).
- An epic’s points are not added up either. Story points don’t roll up from stories to their epic (JRACLOUD-90636), so there is no epic total to group in the first place; see Sum story points from subtasks to epics in Jira.
- Plans, on Premium and Enterprise, groups a plan’s timeline by assignee, team, sprint, release, label or component (Atlassian), and rolls estimates up the hierarchy; see Roll up in Jira without Premium.
An export (free, a few minutes)
Atlassian’s own answer for story points per assignee is a search and a spreadsheet (Atlassian):
- Search for the work, for example
project = WEB AND sprint in openSprints() ORDER BY assignee ASC. - Add the Assignee and Story Points columns. A team-managed space calls its field Story point estimate.
- Export to CSV or Excel, and total the points per assignee, with a filter or a pivot table.
That totals the stories each person holds. For epics, add Parent as a column and total by parent first, then by the epic’s owner, which is a second lookup in the spreadsheet.
With Sumline
Sumline is our app. Its table, in a space’s Sumline tab or under Apps › Sumline across spaces, has one row per epic or initiative with its points, time and both percentages, added up from everything under it. Group by then gathers those rows:
- By assignee, priority, status or team, by type, sprint or fix version, and by space across spaces. A grouping that does not apply to the rows, such as Team on a site with no Team field, is not in the menu.
- A shaded line over each group with the group’s points, original estimate, logged and remaining time, work items, and both percentages worked out again from the sums.
- Nothing counted twice. An epic inside its initiative’s row, in the same group, counts once, and the line says which on hover.
- The same lines in the downloads, marked “Total” in the Type column, and in the address across spaces, so a link opens the same grouped table.
What it groups is the row’s own field: by assignee, that is the person the epic is assigned to, not each person who worked on its stories; by team, the team in the epic’s own Team field, “No team” last. For points per person in a sprint, the export above is the way. More in How the numbers are calculated. For every epic’s progress on a dashboard, see Jira epic progress chart and report on a dashboard.
