We have multiple people working on a single story (back-end testers, front-end developers, testers etc.). How can I get this view for just their sub-tasks? Because using this feature, it aggregates the effort (in hours) against the person whom the story is assigned to.

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?

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).

When i created JRA-23864 i had the same problem in mind. The idea behind the issues is the same but the way it is solved is totally different.

I agree with this issue.
As with any type of planning, in the end a task should be assigned to a person.
Then it is essential to know the capacity for that developer and how much of that capacity is already taken. Without this feature scrum masters have to tally up the numbers themselves.
Per sprint/per resource you should have the ability to:

• calculate the number of working days (by using startdate, enddate end possible holidays)
• Subtract a percentage for support hours (time spent on the phone or answering emails)
• subtract a percentage for "lost hours" (getting coffee, listening to the boss, going to the toilet, etc...)

Any progress with this? I disagree with 'Minor' prioritisation, this is a MASSIVE issue and is a blocker for us migrating our projects from the Classic boards (which does allow this via the use of contexts).

The largest scrum team I operate is 14 engineers who are, for the most part, specialists and unable to assist each others tasks - as such part of the planning activity is assigning to individuals. Before I start a sprint I NEED to be able to quickly check the capacity of individuals to look for under/overloaded individuals; simply knowing how much time is assigned to the team as a whole is insufficient.

We don't operate any teams of pure generalists, and in my experience these are actually pretty rare. As a ScrumMaster I REALLY need to be able to balance task loading as part of planning.

+10000000000

This is something which is trivial to do in the Classic Planning board as it was possible to create 'Per user contexts' - this would allow you to filter by user, you could then look at the upcoming sprint version and the 'Time Estimate' would be for only the tasks assigned to that user.

I have large teams with numerous specialists where several members are individually loaded, in the planning view I need a way to see the time estimates for those individuals - with the new planning board this is not possible and can only be achieved by manual tallying (which with 300+ tickets is not ideal) or by starting the sprint and creating a filter which queries specified user and relevant sprint ID - however if I need to change anything at this point it appears as scope added/removed on the report and on the charts.

I look forward to using the new boards but the lack of this functionality is a blocker so I hope it will be addressed soon.

Greenhopper would only really be useful to my organisation if I could (in scrum mode);
• Create tasks – ok
• Add them to a sprint – ok
• Assign durations in hours to the tasks – ok
• Assign the tasks to one of a number of developers – ok
• See the total assigned estimated hours for the sprint, per developer...

I want to be able to see if the work assigned per developer fits in the sprint. I need to see the total time for tasks allocated to each individual in a team, and compare that to the availability per individual, taking holidays into account.
My developers are not interchangeable, and I would need to balance the sprint resource budget per individual.

Jackie

This has come up a number of times in a few companies that I've been associated with. Is it possible to "up" the priority on this one?

Thanks!

FYI - We purchased the Tempo plugin recently to provide this functionality that GH does not have.

Our team would love to have this!

Is there any plan to include this feature in an upcoming release?

Hello,

this feature would help us extremely! I am currently using Issue exports to Excel to be able to identify over-allocations of team members taking into account their holidays.

I don't understand why this feature is marked as "minor". It should be of high priority.

Don't forget that your target audience is not the Open Source community, but companies paying for your solution. These companies often have to perform fixed price projects. For these kind of projects, it is a must to be able to track the team member assignments. Otherwise, it is not possible to guarantee a specified delivery date.
Time-boxing does not really apply for these projects. Nevertheless, the agile methodologies and tracking abilities of Greenhopper still help a lot.

Please add this functionality as soon as possible.

Thanks.

Hello!
This is something we really need too! It has a heavy weight in our go/no go decision regarding the Atlassian solution stack.

We have full time and part time developers, and their availability is different (each developer has a separate working calendar. We have to manage the capacities in hours per developer / day. Maybe Team Calendar is the best place for this information.
I have also tested "agilo" from agile42.com, and their approach in this question would cover our issue.
A related nice-to-have option would be a burndown chart per developer.

Thanks,

Tibor

+1 vote.

This functionality should be implemented ASAP, definitely.

Thanks,
Mariusz

Really useful!

A possibility to perform individual planning and get the charts showing more correct estimates in GH would be super. Typically the team member himself (or mgr) should be able to globally set the members total availability (working days, hours/day, vacations, total assignment date range etc) and then have a feature to distribute the availability over multiple projects.

I typically work with more than one project in parallel and do not participate full time (i.e. part-time + multiple assignments)

A manager report showing the individuals total planning (all projects) with planned history, logged work and future planning could be useful as well.

+1 vote.
We proceed almost same as described,
Our current workaround is by Excel Export.
It's convenient for weekly report but not convenient for re-shuffle (i.e during team meeting review).
During production, delay always happen and shuffle workload, base on remaining workload vs capacity must be easy and online.

Thanks,
J

This would be really useful for us - we have a team distributed over two countries so it would be really useful to be able to log non working days per team member.