What is the challenge? There is a standard field called Duration (weeks) in Frameworks. However, some tasks are performed daily, such as "review ideas". It would be better if this wasn't coded to read "Weeks". What is the impact? I cannot easily u...

We are measuring engagement via the idea portals. We'd like to be able to see how engaged and institution is with us and one of the measures we are using for that is how many people are registered for the portal. In order to get this information r...

Currently, only the changes made to a JIRA issue are sent over to Aha! through the webhooks. We should have a way to force Aha! to synchronize all descriptions and fields from JIRA for an entire release.

Currently, I can filter list reports by top 5/10/25/100 rows. This is really useful to focus on ideas or epics with the highest priority. This "top X elements" filtering is still applied when adding the view to a dashboard. However, when I insert ...

It would be great to have the ability to automatically publish a report into Slack whenever a presentation is created or updated

Why this is needed: I use the feature board view a lot to discuss our new-feature plans with engineering. As and when we make decisions, features can move sideways (e.g., from a Parking lot to a named release) or up and down (e.g., in a single Par...

Who would benefit? All product and develop teams What impact would it make? Ensure the prioritized backlog is tidy How should it work? Moving a feature from the workflow board to the prioritized backlog should automatically unassign it

After you've been using Aha! for a while, the number of epics builds up. This can be come a hinderence when you are looking to add a feature to an epic and the drop down list has dozens of results. After speaking with Aha! engineers, it was pointe...

In this scenario, there is one Program product workspace in Aha! and one Program project in JIRA which contains Master Features per Agile Release Train. All Stories (Aha Features) and sub-tasks (Aha Requirements) are with one or many Agile Teams (...

We would like to be able to 'lock down' some fields unless there is approval to change them. For example, Release date (or due date) Budget Designated people in the company would be required to approve any changes to these fields. Along with this,...