What is the challenge? Capacity planning should not over-allocate a team's daily capacity What is the impact? Unclear on teams capacity Describe your idea Capacity planning should not over-allocate a team's daily capacity, but rather...

What is the challenge? As project managers it's common that we track resources, including logging time for them and getting estimates. With the current Aha capacity planning, only the user logged in can log their own time. This creates issues wi...

What is the challenge? Our organization regularly conducts prioritization exercises for the projects (releases) we have in the development pipeline, which provides guidance to our R&D team for planning future work. There is no prioritization...

What is the challenge? Only part of the Epic is visible currently (unless you hover). I need the entire Epic title to be visible for a milestone in a Custom Roadmap (without needing to hover over it). What is the impact? I cannot use Custom Roadma...

What is the challenge? Right now, if you want to reuse a workspace prefix, you have to follow many steps including deleting all previous records with the prefix assigned. This can prove challenging with parking lot releases that cannot be delete...

I have certain fields that need to be filled in before moving to the next status in my workflow. The data for these fields is not known in the previous statuses, so it can't be set as a required field before the record reaches a certain status. Th...

What is the challenge? Custom saved views set as workspace template defaults don't dynamically filter to the current workspace like Aha!'s built-in default views do. If I save a customized Features Workflow board view, it shows whatever static w...

What is the challenge? Currently, where a Jira Board is set on an integration it cannot be edited or removed. What is the impact? Customers who are not mapping the Jira Sprint field do not need to select a Jira Board. However, once the Boa...

Currently mapping the Aha! "Release name" field to a Jira Label (type: string) field is not supported. While the team is able to map the field to a text field in Jira, it has limitations for querying and plotting chart. This idea is to support map...

What is the challenge? Aha! webhooks can currently be triggered only by changes to a set of standard fields (name, description, status, assigned user, dates, etc.). Many teams rely heavily on tags, record links but changes to these fields cannot...