Friday, July 13, 2012 9:38 PM
I’m configuring a CQ to TFS two-way sync.
I am using the CQ column “Component” to map to the TFS column “Area Path” and using a ValueMap to do that (two separate ValueMaps, one for each direction).
Going from CQ to TFS, I would also like to use the CQ column “Component” to assign an initial TFS “Assigned To” user. I want to again use a ValueMap and for each component, assign the bug to the Dev Lead for that component. Going from TFS to CQ, I want the “Assigned To” to be mapped to “Developer” (simple mapping with a Users ValueMap).
I am having issues because I am trying to use Component as the “LeftValue” for more than one field mapping (first for “Area Path”, second for “Assigned To”). Does anyone have any recommendations for resolving my issue?
Tuesday, July 17, 2012 5:39 AMModerator
Thank you for your question.
I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience.
Thank you for your understanding and support.
Cathy Kong [MSFT]
MSDN Community Support | Feedback to us
Friday, July 27, 2012 12:33 AM
Don't think you can do that because I can't think of a way to pull parts of a field. You can use an aggregated field to move to 2 different fields
This posting is provided "AS IS" with no warranties, and confers no rights
- Proposed As Answer by Brad Peterson PSS MSFTMicrosoft Employee Thursday, October 18, 2012 5:53 AM
Monday, August 06, 2012 5:35 PM
So it sounds to me like the tool will look through the field mapping elements and probably take the first one that matches the source and use it. Therefore if you have two entries for the same field in the source, it will ignore the second one. Am I close?
Once again, just to be clear, I want to do the following
Component --> Area Path (via ValueMap)
Component --> Assigned To (via ValueMap)
So that is currently not possible today?
FYI, the reason I want to do this is because the QA folks (the ones using CQ) really do not know who should be assigned to a bug and therefore I figured they could just assign the Component, and I'd use that value to map into the appropriate developer (or dev lead for that component)