Our product team has just started using aha to keep track of product development. Mean time in the individual teams we are free to choose what ever tool we like and fits our needs, and for that I've chosen coda.io. Coda.io have a feature where you...

Providing and ‘Aha! for EMM’ (Enterprise mobility management) app version will make it much easier for some companies to get governance board approval to use the mobile app.

We would like to see our work estimates by other fields not captured in the standard capacity report by creating a custom report. We are using the field "Week start" to show the estimates by month and those additional fields. However, we don't wan...

For a customer persona field, we would like to limit the Personas allowed to a defined level of product lines. So, the Product line immediately above the workspace, or 2 above. Or even by citing/naming the Product Line which would be the highest l...

Related to https://big.ideas.aha.io/ideas/APP-I-5692 In addition to adding fields lower in a layout hierarchy, it would be good to be able to remove ones that were not "essential". For instance, one of our teams (with a product line) do NOT want p...

We're working on an integration where we'd like to know the plan name for the product. For example we'd like to distinguish whether the plan is Ideas Advanced or Ideas Essentials. On the similar lines we'd also like to know for Roadmaps the plan n...

When exporting information for an epic/idea/feature, there are no choices for what gets exported. It only exports the details, sidebar information and attachments. Please consider adding some type of selection where the user can select export deta...

We primarily track external release dates. Aha assumes that we track internal release dates and that presents several issues: Forces us to input internal release dates on the Create Release page Does not allow external release dates to be set on C...

In Jira, we track external Release Dates. Aha does not allow external release dates to be synced. This means our Jira is reporting inaccurate information.

We might not want to initially use the Requirements sections due to our integration with TFS. It would be good to be able to hide sections on the Requirements form, and also be able to make the visible again should we decide to use that functional...