All ideas

Showing 1396

Use a single email address for Aha activity updates

Our corporate Outlook 365 account dumps around half of Aha activity email updates in spam, which kills a lot of what makes this kind of tool useful. My best guess is this is likely due to Aha setting a unique identifier for the from address of eac...

David Marble over 6 years ago in Comments / Notifications 0 Unlikely to implement

4 VOTE

Allow Idea Comments and Attachments to Map to Features, So they can be Mapped to JIRA

Currently Idea comments & attachments don't carry over to Features. If possible, we'd like to configure features so these components carry over.

Guest almost 9 years ago in Ideas 1 Unlikely to implement

3 VOTE

Need option to disable orange circle notifications (for nervous people)

In the notification preferences I can not disable notifications on the user menu avatar and on the favicon without disabling email notifications. I find the orange circle on the favicon distracting and would like the ability to disable it.

Guest over 6 years ago in Comments / Notifications 0 Unlikely to implement

3 VOTE

Allow field-by-field selection when linking Aha and Jira records, rather than all from one or the other system of record

When I create an epic and link to an existing JIRA, it asked me to choose which summary, name, description info to use. Would be nice if I can select which field, i.e., name, summary or description, to use from either JIRA or Aha. As it is now, it...

Kirstin Maurer over 6 years ago in Integrations 0 Unlikely to implement

4 VOTE

always create Fogbugz cases as 'Features', not 'Bugs'

Currently, whenever an Aha feature is sent to Fogbugz, it is marked as a 'Bug'. They should start out as a 'Feature'.

Guest almost 9 years ago in Integrations 1 Unlikely to implement

3 VOTE

Enhance Trend report to include projected/forecasted line

This idea to suggest an enhancement the 'Trend' Report type to include an additional generated future trend line to forecast where the trend of existing data is headed. The screenshot below has a green dotted line to illustrate how the proposed fo...

Tom Bailey over 6 years ago in Reports 0 Unlikely to implement

4 VOTE

Add ability to configure what sections are visible in the Requirements form

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...

cheryl fetchko almost 9 years ago in Features 0 Unlikely to implement

4 VOTE

Show delivery of requirements across releases

Today there is no good way to show the delivery of requirements for one feature spanning multiple releases. For instance, if you have 3 of 4 feature requirements being delivered in Release X, but the feature itself won't be delivered until Release...

Micaela Heck almost 9 years ago in Features 1 Unlikely to implement

3 VOTE

Address usability when working at scale

It is clear to me in many aspects of the UI consideration has not been given for working at scale. For example: Our tag list has grown to several thousand entries and yet I can only prune the list one entry at a time. Our product tree has over one...

Andrew Foster over 6 years ago in Application 0 Unlikely to implement

4 VOTE

Deactivating Users

Currently when deactivating a user, the user then becomes 'greyed' out. This isn't readily obvious due to coloring, resolution, etc. Suggestion is to clearly annotate the user with a Joe Smith - Deactivated or something similar

Joe Carpenter almost 9 years ago in User management 0 Unlikely to implement

Share your product feedback

Please enter your email address

FILTER BY CATEGORY