All ideas

We have a lot of custom fields that have been added to the Master Features and Features details sections. Some of them are quite small fields (see attached). I'd like the ability to move those fields next to each other, instead of having them popu...

you should be able to click on attachments/images to view an expanded view of the image from the description box. Right now they appear in the description and many times are used to describe bugs or new features, however the preview is too small f...

Currently when images are added to a text areas in Aha!, the image is resized. This can occur even when the image width would not exceed the width of the text area. It would be really nice to have an option when hovering over the image to return t...

Rally has a concept of Backlog where the Release is set as 'Unscheduled'. But there is no way in Aha! to assign a Master Feature or Feature to something like 'Unscheduled' so that the Release information does not get populated in Rally. We want to...

We deliver customer solutions on top of our base product which often drive the development of (future) features in our base product. Because we have to manage these features separately as part of delivery of this customer "product", we then find w...

I want to search for features / releases that are not shipped yet. Currently, the aha REST API does not offer "workflow status" as a search parameter. Further, the API response does not indicate the status in the feature/release "shortened" json r...

At this point new to-do's email notifications takes affect from general notification settings and user either gets lots of email or none until to-do's due reminder sends email notification. Our need is that new to-do's should either always send em...

http://www.collab.net/products/teamforge Our development team uses Collabnet and as much as I would like to convince them to use Jira I do not think that is a realistic possibility, so this is a request for Aha to integrate with Collabnet.

Aha! Develop allows teams to have a unique layout for features and requirements. This helps them see the information they need for development, while hiding the information they don't. Please support this for epics as well.

I would like to display the 'description' field available in the scorecard configuration section on the actual scorecard displayed when in features, ideas or other areas the Aha! scorecard is viewable (image #2 below - without creating a bunch of ...