Skip to Main Content

Share your product feedback

ADD A NEW IDEA

All ideas

Showing 411

Deleting a feature or requirement should delete the linked Jira issue(s)

When I delete a feature or a requirement in Aha!, I then have to go to Jira and delete the corresponding epic or story. Would love it if deleting a feature in Aha! deleted the linked epic in Jira and all stories for that epic. Likewise, deleting a...
Guest over 10 years ago in Jira 11 Will not implement

Include "Comments" when exporting a single feature

It would be great to have an option when exporting a single feature to have it include the comments. I state as an option because there are instances when the comments are not necessary but for others it is quite necessary.
Guest almost 8 years ago in Features 3 Will not implement

Add option for adding use cases

What is the challenge? What is the impact? Describe your idea
Guest 9 months ago in Strategy 1 Will not implement

If a comment is deleted in Jira, please delete that comment in Aha! also

Some comments are for testing purposes or are not correct. If we have decided to delete a comment from an epic or story in Jira, we would like it to be removed from the feature in Aha! as well.
Kelly Sebes almost 7 years ago in Jira 1 Will not implement

Dependancy Map using already existing relationships

We have an Epic (Initiative) - Feature - Requirement breakdown structure. It would be very useful to be able to visualize the dependencies using these existing relations instead of requiring to add separate link specifically for the dependancy map.
Kenneth Palm over 8 years ago in Features 1 Will not implement

Add folders to Reports-Dashboard drop-down

I love the Report Dashboard, but now that I've created a few folders, I want to be able to access them directly instead of going back to the main page. Add a Folders choice in the Reports drop-down. Extra points for selecting reports to be immed...
Max Cascone over 7 years ago in Reports 2 Will not implement

More granular notification control at the entity level (e.g. ideas vs features vs requirements)

Hello, We would like to have the granular notification control that you've rolled out at the product level (e.g. none, instantly, hourly, daily, etc.) to be extended to the *entity* level (e.g. ideas vs features vs requirements) so that you can ha...
Mark D over 7 years ago in Comments / Notifications 0 Will not implement

Ability to disable attachments in email

As a security manager and Aha! administrator, I'd like to be able to disable attachments from being sent in emails to ensure that security policy is followed and that all content shared in/via Aha! requires a login.
Scott Goldblatt almost 8 years ago in Account settings 0 Will not implement

Pivotal Tracker Integration Mapping

It would be helpful if one of the mapping options with Pivotal Tracker could include the following options: Master Feature to Epic Feature to Story Requirement to Task Instead, the only option for mapping to Epics in PT is to use Initiatives. Th...
Tom Beck over 6 years ago in Pivotal Tracker 1 Will not implement

More complete field mapping between Aha! and FogBugz

Both products are feature rich and have many alignments which would be great to keep in sync. Aha! Feature Type - FogBugz Case Category FogBugz has an "Area" concept which doesn't map directly. At least being able to select the target area for ne...
Guest over 9 years ago in Integrations 4 Will not implement