All ideas

At the initiative level, we plan 6-12 months into the upcoming fiscal year, by half. We estimate team capacity (high-level t-shirt sizing) by 1H and 2H. Our goal is to know the right scope moving forward and balance our engineering capacity for 1H...

As a user, I need the ability to do a mass update on Workspace custom fields so that we can utilize those fields for reporting. All of our products have specific business programs and business segments so we created a custom field to capture progr...

As a Product Manager, I want to be able to add a standard release cadence and if one of my releases gets delayed, the rest of the releases get pushed back as well. For instance, if we have standard 8-week release schedules and one gets delayed by ...

It would be helpful for fields like the Jira key or integration link to be available in automation rules. That would enable my team to create triggers that look at when an integration link is changed or is no longer available.

Currently the release date field is required. But usually when a release is first written up there is no realistic idea for when it might be delivered. For releases that are postponed or of lower priority, the initial entered dates which seemed so...

When someone submits something that sounds like a bug, present a callout and instructions for opening a ticket with support. Callout should be configurable.

Currently the initial estimate defaults to the number of days between the start and end date of an EPIC (and feature). At the EPIC level this can through off our capacity planning if the advance estimates are not updated when the EPIC is created. ...

As a user, I reference several internal documents and templates to do my work in Aha. I would like to be able to search for all record types (Initiatives, Features, Epics, Documents, Attachments) in the same search bar.

As product owners use Aha as the primary repository to develop and track their roadmap, they want to enhance their planning phase by improving the existing configuration between Aha and Rally. Currently, capabilities, features, and user stories ar...

Issue: The ‘To Do’ is represented in two areas in a feature as 1) The ‘To Do’ and 2) ‘To Do – To Do Tab’. With that said, The duplicate terminology naming of ‘To Do Tab & the To Do’ is causing confusion issues with best practice adoption. Use ...