Capacity planning

Currently, throughout Aha! and in the documentation the term Capacity is used loosely to imply both Capacity or Demand. This is creating confusion amongst our users and we request that Aha! clarifies the terminology to distinguish between demand a...

It is possible to configure quick status transitions which is a very nice and quick way to change the status of an item in Aha. It would be excellent to have the ability to quickly log a preset amount of effort against a task as well. This button ...

We are currently unable to grant Capacity Planning Teams Configuration to a specific product line without have the permission being inherited to all the children product lines/products

Management needs to view a summary of the split between CapEx and OpEx costs. A given feature can include a mix of both types of expenses and there needs to be a way to capture the split of CapEx and OpEx within the estimate. There also needs to b...

Hours is a fairly ridiculous estimation metric for a large project being planned for several months hence and requires a lot of cognition to reason about. Yes, we can do math and convert, but the UI shows hours in many places and when it shows day...

What is the challenge? We have some resources whose capacity get split across 2 teams - one team is product engineering, the other is project delivery. There is development work in both teams but from a planning perspective a developer may be sp...

What is the challenge? Can't visualize developer burnup using logged effort. I want the burnup chart to increment each time a developer logs effort. What is the impact? Improved capacity planning, especially for stories >1 sprint De...

What is the challenge? Description Problem When epic progress is based on remaining estimate (“Calculate from remaining estimate”), the rollup only uses Detailed estimates on child records. If a child story (feature/requirement) has only an Ini...

What is the challenge? Assigning work, would it be Epics, Features, Requirements, or whatever item, to an individual is not relevant for us, for multiple reasons : We might assign it from Jira Some tasks require multiple people from the same...

What is the challenge? The way that capacity planning currently works is that you create a schedule with a static number that you label velocity, but isn't actually velocity. Each team's velocity is different and applying a blanket "each person ...