The count in Settings->Integration updates is for all workspaces, including those to which I have no privileges to action.This can be confusing as when user selects the option, there are no updates to process.

The mechanism to bulk select / delete on any work view in aha develop is far too out of sight. - no indication on where to perform this task - falls out of line with roadmaps as the list view does not contain the bulk edit button as it switches to...

When filling out feature date range details, it should be an option to select a fiscal quarter or fiscal year as a drop down. This is in the feature overview tab.

The workspace settings report is helpful when managing a large account and changes need to be made. Accessing the report is somewhat buried within the associated workspace's settings area. It would be nice to be able to quickly run the report as a...

after embedding a hashtag link to a Feature or Requirement, I'd like to see the name of it when I hover my mouse over the link. The requirement number that gets embedded isn't always helpful to know what it refers to without going there.

There is no transparency for submitting ideas and watching them be pushed to production for non developer folks. If someone submits an idea they should be notified when: It is converted to a Feature It receives the status "will not implement" The...

The history file only includes creation, updates and deletes to a record. It does not include views nor does it include downloads of a file attached to the record or comment.

Allow automation of integration setup from other tools. In my use case, the intent is to be able to validate/cross-check what is actually configured on the JIRA side (admin only) with what is expected/desired on the Aha side (various project team ...

Currently, if I was to configure the feature workflow board (and/or feature cards on workflow board), the changes I made would only be reflected back to me. Every user of the workflow board has to then configure the board (and/or feature cards) th...

To-Dos can be defined at different levels of Work Items. Pivot reports should let you have this differentiation to show across all levels based on the report configuration. We would like to show the To-Dos associated with a Release, then the Featu...