Detailed Capacity Planning

No, I am not a watcher on any of these. Moreover, these ideas are not even submitted by anyone from my org.

And again.. Detailed capacity planning.. Guys.. Aha is not a project management tool.

have an idea how to solve it and already proven the concept in my organization. Scorecards! It is absolutely possible to define a scorecard and on this basis a report that would track skillset type capacity per feature. And aggregate in reports. Also.. there are custom tables..

This would be Amazing!!! real GAME CHANGER, would really allow for all in one place! 

Effort/Resource and Elapse-time could be communicated on a roadmap by varying a feature/epic line width over time. Would really love to see this.

When will this be launched? 

Bump on this - please give us an idea of when this may be available!!

Hello, any indication on when this feature will be implemented? It was added 5 Years ago and says Release time frame 6 Months. Does this mean it will be released this year?

Is this on the road map for this year?

This would definitely help in the cases where a single resource or team cannot allocate all of thier time to a feature.  It would be nice to be able to define % allocation, so that if this is 50%,  the time it would take to complete is twice as long.

This could also be solved if customer field could be a calculate value from other fields.  You would add a customer filed for % allocation, and the time interval could then be based on estimated hours * % allocation.

We would love to be able to add our estimates to the remaining estimate field in Aha and then when the work is logged against stories/tasks in Jira, have that burn the remaining estimate down in Aha.

Even if we could define scrum team capacity within a release (i.e. Scrum 1 = 100d, Scrum 2 = 200d, and Scrum 3 = 100d; Total Capacity = 400d), and then associate each feature with a scrum team, so that we can see when we've exceeded the capacity for a particular scrum team -- that would be immensely helpful.

I have posted already one thing in comments here: "I believe that the planning should be done around teams not individuals (and definitely NOT RESOURCES)." I would like to elaborate - would be great to actually track capacities of teams via aggregate burdown charts on product line level below which multiple products with 1-N product teams work. In fact it is requested.

But I would like to add my 2 cents to requests from project managers:

1) AHA is not project management tool and I don't believe it should
2)¨AHA is a product management tool and therefore the apetite for absolutely absolute metrics and final numbers so that fixed goals can be evaluated, tracked and aggregated seems to be rather misplaced
3) AHA is not at its final stage of evolution and I am sure it will get more features and superpowers to measure progress and report on it. But in a fashion of relative targets, rolling metrics and modern industry principles (apologies to those that use aha for construction work management and want to estimate usage of bricks).
4) AHA promotes strategy and initiatives over projects and budget. 

Whenever I say "AHA is" or "AHA is not", I mean "I sincerely believe. And I do believe in AHA mission...

We would embrace this update! This would be a huge improvement to our planning.

I'm very keen on this (product owner at a 2 year old SAAS startup).  Current use case: we have a few teams with separate specializations (front end, back end etc) and each has a capacity which needs to be separately managed and utilized - I'd like to estimate the work for each team separately either at the Master Feature level, or at the Feature level once we start breaking it down closer to implementation, so the roadmap is based on realistic capacity plans.  Being able to map these teams to custom fields in Jira so we can plan and track sprints somewhat separately (even if just using filters) would be very useful.

A related issue is that we continuously release product updates each sprint rather than having specific releases. Right now I'm setting up lots of releases (quarterly, further out, then monthly as things get closer) to plan capacity and ensure that the roadmap is somewhat realistic.  Having something more suited to continuous releases like this would be very useful.

What happened to this feature? It looks like it's been about 4 years since it was suggested, yet nothing has materialized - are there still plans to include proper resource management into Aha?

In our team we're currently looking into alternatives to Aha exclusively because Aha doesn't support separation between "programming time" and "design time", an essential requirement to proper time estimation in our situation. If aha supported having several separate capacities we would not be forced to swap to a project management software that supports this functionality. An update would be appreciated!

The key for my team is having a fully supported Sprint object. One that has a defined start/end, can contain many releases across different initiatives, and can be used for scheduling on a roadmap view. Right now I constantly need to refer to the sprint schedule when putting in dates to ensure they align, would be much easier to just manage releases between sprints vs free-form dates.

I would really like to see this feature. It would be great to be able to enter resources and locations and have weekends and holidays be automatically calculated. The goal of this feature is to avoid having to use a project planning application to calculate resource capacity.

It would be nice to have possibility to calculate and show in reports Feature percentage finished, based on Original and Logged effort, both as a number and progress bar.

I've been using Aha! for a couple years now and am tired of waiting for this critical aspect of product management.

I've appreciated the recent efforts around integration improvements. However, how have all of your reporting updates been prioritized over providing useful capacity planning?