This idea has been merged into another idea. To comment or vote on this idea, please visit APP-I-1743 Set the TFS Iteration and Area path per feature or requirement.
We have several development teams on our product, and each has their Team defined under a single TFS Project. It looks like the current TFS integration can only push features to the default team (which is associated with the Project itself). Each team has their own workspace in TFS and can only see features created within that team space. However, in Aha, all those features are under the same Product. So, I'd like to be able to send features from Aha to different Teams in TFS, depending on the story. Maybe a field on the feature that pulls the list of Teams in the TFS Project?
The TFS configuration should allow the administrator to specify a subset of the Teams available for selection in Aha. For example, our company shares one project, so my product teams are mixed in with the others, and I don't want to see the other teams in the drop-down on my features in Aha.
I don't see a way for our product (or any other with multiple Teams) to take advantage of the integration to TFS without this capability.
|Release time frame|