Please see the release notes and blog post for new functionality in JIRA Agile 6.6 which can help with capacity and utilisation planning for specialists in teams:

http://blogs.atlassian.com/2014/09/jira-agile-6-6-now-available/
https://confluence.atlassian.com/display/AGILE/JIRA+Agile+6.6+Release+Notes

Regards,
Martin
JIRA Agile

I would really like to see this PLEASE.
I'm constantly asked for this functionality and similar task management functionality from many different projects and various functional groups of those projects.

Thank You.

A related feature which helps with the visibility of assigned work for specialists/team members will be released in the upcoming JIRA Agile 6.6 release. Noting here because it has some overlap with the needs of this story and may help with you planning needs:
https://jira.atlassian.com/browse/GHS-9689

Regards,
JIRA Agile team

@Jim Reed, this is exactly what our team needs as well. We just did sprint planning (our first full sprint with JIRA Agile) and we found this to be a pain point.

I don't see how dates have anything to do with this. It doesn't matter if a Sprint is 2 weeks or 20 weeks and it doesn't matter when the Sprint occurs. All I need to know is for a particular Sprint, how many story points and/or estimated time is assigned to each assignee.

Example:

Sprint 5:
Assignee 1: 65 story points, 78.5 hours
Assignee 2: 78 story points, 93 hours
Assignee 3: 43 story points, 58.2 hours
Assignee 4: 58 story points, 63.4 hours

When planning a Sprint we drag stories from the backlog into the Sprint we are planning, provide a time estimate and assign it to a developer. The problem is there's no way to easily see if one developer has too much assigned to them and another doesn't have enough. Having this capability would dramatically help with Sprint planning. I don't think this capability is really necessary for planning Sprints in advance since it's too low level, but if I'm planning the Sprint that will start tomorrow we need to make sure everyone knows which stories they are responsible for and that nobody is over or under utilized.

I think this is more important for time estimates than story points since story points are more for long term higher level planning and are only set on the stories. A story may have multiple technical tasks which may be assigned to different developers. So seeing the total time estimates assigned to each assignee is critical.

I fail to see how this could be accomplished without first supporting dates on future sprints. What am I missing?

This seems like such a glaring omission in the latest JIRA Agile. I used the old Greenhopper at a previous company and was able to summarize the total estimates by assignee, but the new Agile is completely missing this capability. Searching on Google I see tons of people asking about this capability. The common response is "In Agile you shouldn't pre-assign stories in a Sprint", but this is complete RUBBISH. I can understand this at mid to large organizations, but in a small organization where developers skills are specialized and certain stories/tasks can only be completed by specific developers, it's critical when planning a Sprint to make sure the stories you commit to in a sprint have the proper skill capacities, and the only way to do this is to view by assignee. There is the user workload report, but it only reports time estimates (no story points) and you have to run the report manually for each assignee rather than seeing a summary of all assignees. It's easier to just export the issue list to Excel and sum the story points by user, which is a hassle during a Sprint Planning meeting.

Is there any simple way to show the story points and/or estimated/remaining time estimate per assignee per Sprint?

Would greatly appreciate this feature! We have employees in several different countries working on the same projects - and the non-working days are not the same from country to country - so to be able to log when a team member has holiday or public holidays for that country would have a significant influence on our planning! Thanks for considering to introduce this.

This is the only feature I think Rally covers better than JIRA AGile (formerly GreenHopper). The ability for a developer to set their capacity so that a PM / Scrum Master can assign them stories appropriately is essential in an enterprise environment.

+10000000000 pts too!

• In a first stept it would be sufficient to suggest all developers to have the same velocity (group_velocity/nr_of_members).
• velocity based on story points
• The version report diagram should shift according to resource availabiliy (of course for version release date planning but also to test how releases get earlier with more manpower).