It would be great if we could have Initiatives sync over to TFS as Initiatives or Epics to get the full hierarchy tracked in both systems. As it stands, we have to manually create initiatives in TFS and then link the Features up to them. Adding it...
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...
TFS (a.k.a. VSO) Automatically create new stories in TFS as requirements in Aha! when stories are created under a linked feature.
If a feature has been sent to TFS as a feature and requirements as stories, when I create a new story under the linked feature I would like it to be automatically created in Aha! as a requirement.
The integration with TFS has a lot of potential, but it's still work to have to remember to click the Action then Update TFS. If some product owners forget, then we have to audit what features and requirements are in both systems and see which one...
Aha! integration with should create a hyperlink record in TFS to link back to the Aha! item
Aha! integration with TFS should create a hyperlink in the TFS item when the Send to Team Foundation Server action is selected and a new TFS item is created. Additionally, an action that sends a link record to TFS would be helpful if the link is l...
Epics on top of feature were introduced with VSO a few weeks ago.
The VSO Connector should be able to reflect that somehow. Either by also working with epics in aha that encapsulate features or better the easy MVP way with a global setting for the...
Aha! Feature Rank should be sent to TFS during integration updates
We currently have to use the Feature Board in Aha! to prioritize the features. and then we have to use the Feature Board in TFS to apply the same order. The Feature Rank is not included in the integration with TFS. We need a process that synchroni...
TFS import should create a link between Aha! features (and requirements) and TFS issues so that when we import to seed the Aha! account, we can keep the entire history of the TFS issue.