If you look at your sprints in plan mode, you see the people that are assigned work in that sprint just below the sprint start and end date. To the right of the people, you see 3 dots, which when clicked will open a summary showing every assignee and the number of issues and associated story points assigned to them.
This was introduced in JIRA Agile 6.5: https://confluence.atlassian.com/display/AGILE/JIRA+Agile+6.5+Release+Notes#JIRAAgile6.5ReleaseNotes-AssigneesshownonboardsinPlanmode
Geert, unfortunately your solution only works if all resolved issues are still assigned to the developers who resolved them. If issues are already reassigned, e.g. to QA or review people, they don't show up next to the developer who resolved them anymore. Does anybody know a way to show all issues RESOLVED by a developer, summed up per developer, per sprint? Thank you!!
I have the same question to Shlomo. I know another team do this by creating separating tickets for 1 change (e.g. 1 ticket for analyzing requirement, 1 for development, 1 for QA, 1 for deployment...) so that ensures if different person works on the same issue , the story points can still get counted correctly... but I thought there must be a smarter way to do things.
Absolutely. In a sprint, there should be an out of the box report that shows the number of story points completed per assignee. There is already a JIRA pie chart report that displays issues per assignee within a sprint. It doesn't seem like a stretch to replace the issues field with story points.
The only way I have found to do this is to search the issues using a standard query like:
project = XXXX AND status = Closed AND Sprint = 1234 ORDER BY assignee ASC
You can then export that report to Excel and sum by developer.
With that said, it's a real shame that we don't have a better way of reporting on sprints after they have closed. I know it's not perfect, but it would be very helpful to know how many story points developers are completing per sprint. While I realize it's not the perfect metric, it's still helpful in determining developer productivity.
I finally solved this using the SumUp module.
1) Install it from here:
2) Configure it to sum up story points
3) Create a filter for your sprint
4) Add a 2 dimension SumUp gadget
5) Select user for x and status for y
Thanks Elias for this quick setup.
I believe i got what i need but what i did is this..
5) Selected Report for x and Sprint for Y
so i can see each sprint how many story points are completed by reporter.
Now i build two Dimensional Gadget report, My Y-Axis doesn't show columns (Sprint) in proper order. Is there a way to apply "order by" so it can display in right order. For example, Left to right mean Sprint 1, Sprint 2, etc...
Any help greatly appreciated.
I am looking for this too. The only thing remotely close to this is I can do a Workload Pie and see Original Estimate, Time Spent, and Current Estimate by Assignee, but there is no Story Point option that I can see. It, too, is limited only if the issue remains assigned to the Developer.
I also have some concerns with that context. When i plan my next sprint, i easily get the sum of story points but i just want to get the distribution of story points per user, so that i can evaluate if my distribution is quite balanced among all the users.
I'm happy to see that i've 200 story points to handle in my next sprint, but i want to know if user A has 150 story points and user B only 50.
For me it's a kind of abvious feature to have. Any way to get this in JIRA ?
Geert's solution works great if you're looking at the current sprint. Here's what I figured out for retro sprints. If you'd like to know how many story points scored per user, view the past sprint in the Sprint Report, on the right side of the Completed Issues table there is a link to View in Issue Navigator. Once you've clicked that link, sort the list by Assignee, then click the Export this current filter as a CSV. Open the CSV in Excel, then you can sum the story points for each user easily from there. Hope this helps someone.
Eventually we developed the following solution:
This approach requires you to have the JIRA administrative rights. The main aim of this article is to help you achieve an organized, easy-to-maintain workflows in your JIRA instance thereby, reducin...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs