Despite your careful research, consideration, and planning - that epic you fought for inclusion into a release just isn't going to get started any time soon. Sprints later you realize that it's probably not going to happen ever. Holding on to hope...

User flow: When writing up the description for Release or Epic or Feature I have ability to paste in the image. In the release description I would usually paste in mockups for each step of the journey (can be up to 100 images). Each pasted image t...

Use case: ideas portal submitter has idea for product/process enhancement that could benefit more than one product or portfolio > they can submit via one form v. completing the same form several times for their idea

The API currently only accepts a single value search parameter. There is a requirement to be able to pass multiple parameters/values through the API. For example, execute a search through the API for features that contain 3 specific tag values.

The intended use of GH integration is the following: Create features in Aha Push to GitHub as a handover of control to engineering Updates in GitHub trigger status changed in Aha This is a good start. If control is passed to engineering to manag...

On the starter roadmap, the dates are displayed, but the weeks start on Sunday and run through Saturday. This isn't super helpful and there isn't a way to only display M-F. The extra days are distracting and give the impression of more days availa...

Currently there's no way to determine if the given custom field is display in the create or view layout.

The Prefix for all Master Features is 'E', this is a suggestion to change this globally to M to align with the default terminology. EG PRODUCT-E-123 should be PRODUCT-M-123 instead.

Sometimes you don't have the scope of your items right and end up creating a Release that really should just be a Feature. Please allow the conversion of Releases to Features.