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.

I would like to build a report that shows me ideas that have both the 'From-CSC' tag and the 'iq' tag. As far as I can tell, I can't do this right now.

When moving a requirement from one feature to another existing feature it would be really helpful if you could search by just the Feature # or referenced. In order to do this today you have to know your entire feature number prefix and all. This m...

Currently, there is no ability to notify assignees of a feature (aka project) due date approaching. Every project has a different length based on resourcing, project type, client need, urgency, etc. As such, we need the ability to notify assignees...

When a Jira story is moved from a non-integrated project to an integrated project, and placed under an integrated release, the story is not imported automatically into Aha! An update to the issue is required to trigger the webhook and import the i...

Currently, when generating reports for releases, it provides you with a standard field called "Release features count" to include in the report. However, there is no standard field for "Release epic count" which can be extremely helpful in our env...

Who would benefit? All users looking at relevant tickets What impact would it make? Simplify the statuses to reflect the statuses we use, not the generic categories How should it work? When clicking on the relevant tabs, I would see as the options...