My scenario is that I have each Aha product linked to multiple different projects in Team Foundation Server (TFS), and I want the features in Aha that come from TFS to have a field indicating what TFS project they came from. But I can’t find a way...

We use Assembla for issue tracking and Aha! for Roadmapping. Ideally the two products would be linked to tie roadmap features and milestones to Assembla.

We have been really enjoying the newer ability to include dependencies for features in our Aha-Jira integration, but are running into the issue not getting the same level of transparency for the user stories - to combat this, we would like the abi...

When you have multiple products in Zendesk it would be nice of you could select the product to link to by default, or change the order of the products in the drop down list. This prevents mistakes are made by the support agents.

There are many countries like in Middle East countries have different weekend days than Saturday & Sunday, therefore, it's very important to have the ability to change the weekend days for our planning & reports

Right now you can push a Feature and associated stories to VSTS but if you delete a story in VSTS you have to manually delete in Aha. We need: 1) any story delete in VSTS to be automatically deleted in Aha 2) any story added in VSTS to a Feature...

We use Aha! and it would be great to send and receive work with our partners, who have their own separate Aha! account. Ideally, we could create something similar to a work request (https://www.aha.io/support/roadmaps/strategic-roadmaps/collaborat...

What is the challenge? The product team manages the roadmap in Aha! and the dev team manages the development in Jira. Stories sometimes slide from one sprint to another and the date range of the release is not up to date with the reality What is t...

In Aha! I have a feature with a set of requirements, all of which has been pushed to Jira as an epic with a set of stories. I want to convert one of the requirements to a new feature in Aha! and have the corresponding story in Jira changed to an e...

Github integration messages in comments is great for smaller stories, but for anything non-trivial it becomes very easy to lose meaningful comments in the middle of a commit barrage. It would be very useful to have these either separated, or group...