When stories in JIRA are moved between epics they are not automatically updated in aha. Also, for stories created prior to mapping a JIRA epic the stories are not automatically imported to aha. The import can be used to pull these in but the Impor...

Easily create relationships for traceability on dependent or related features. Manual editing via a dialog box is old-school and very time consuming when working on large products.

We noticed unexpected changes to some epic records relating to their start date. Currently, if a user views an epic in the starter roadmap and the start date is not defined, the date will default to the current date. For features, the start date w...

Scorecards are great, but they do not let me easily rank features against one another. A traditional way to do this is the "pairwise matrix". This breaks ties between features that have similar scorecard ranks. A forced rank list lets me communica...

If a release doesn't have a capacity entered, instead of just showing "n/a", i would like to see the total of the estimates for the features in that release. Extra points: Enable a velocity chart on the feature board. Perhaps a chart can be hacke...

What is the challenge? Filtering out Archived data from current data What is the impact? Impacts custom worksheets and reporting Describe your idea make the "Initiative Archived" value reportable so that it can be filtered in custom worksheets Cur...

When new users are added to products or invited to Aha! (specifically paid users) send an email to the account and/or billing administrators to let them know who was invited along with the user who invited them.

Sometimes notes are taken outside of Aha (by customers, testers, users, project members, etc.) I'd be great if we could use the "Actions" dropdown to convert an Idea into a Note

Goal : to help feature and requirement traceability in a single document delivered at the conclusion of a release. This could also help identifying feature/requirement coverage