It is common practice for teams to have multiple Trello Boards. For example, in our organization, we have our "current development" board with Next Up, In Progress, Awaiting Validation, Completed ... and but like any product organization, you do n...

Having a single area path for the entire product doesn't make sense. This value will usually depend on the feature, as area paths define the area of code impacted by a work item. This helps with evaluating code churn and test coverage. It needs to...

When a user is working on a feature in Aha that is linked to a Trello card, if she accidentally changes the release for this feature to the release of a different product (e.g. the Demo Fredwin cycling product), the trello linkage is immediately d...

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.

Currently, the Salesforce / Aha.io integration requires using a permission set. A System Administrator must assign individual users in Salesforce to this permission set, in order for them to use the Aha.io ideas portal. That's a fine approach, but...

Two-way integration with Redmine.

Two-way integration with Bugzilla

It would be very nice to setup our pivotal tracker integration on a product line. That way if a ticket moves between products in that product line it retains the integration that was configured for it.

Most sprints priorities will change a little bit as time goes on and it will be appropriate to remove a ticket that was added previously. Likewise, if a sprint is over subscribed some tickets may roll over into the next sprint. When this happens, ...

Much like status, it would be nice if tags on features would propagate instantly to stories in PT bidirectionally. We have historically used PT labels to organize aspects of our sprint. It would be nice to setup initial tags in Aha and have those ...