As a product manager, I should have control over the destination of where imported features and epics go so that they are in the release or parking lot where they belong. Today, the destination of imported items seems almost up to chance although ...
In the new integrations 2.0 I can't find a way to set the Iteration Path. While I very much appreciate the new functionality in 2.0 that was a very convenient mapping in order to create work items in a specific Iteration Path.
Allow TFS integration to populate 'Replication steps' for bugs created in Aha
To be able to easily create bugs from within Aha and use the TFS integration to pull across all relevant info from the description field into reproduction steps. After a long investigation by Aha they found that this link was not created as part o...
Given that a PM controls their backlog and roadmap from AHA it would make sense for them to be able to do more than simply send the story to VSO and be subject to changes that are prompted only from VSO to AHA.
For example, if i decide that a feat...
For successful product management and development, User Stories and Acceptance Criteria are key. We want our Product Owners defining not only the user story (requirement) but also the associated acceptance criteria within Aha!. This information wo...
For Project Status, currently the only information we have is feature and requirement status coming from Aha to VSO / VSTS and vice versa. It would be far better for businesses tracking effort to be able to put estimates into either tool synchroni...