Allow TFS Work Item types to be mapped to different SpecLog entities
WE would like to be able to keep all of the SpecLog entities in TFS, but keeping them all as User Stories really doesn't work.
It would be great, for example, to make TFS Features map to SpecLog Business Goals.
-
AdminStephen McCafferty (-, SpecLog) commented
The new V3 plugin for TFS in SpecLog includes the option to choose what type of TFS item to synchronise a card with.
There are some caveats: if you are synchronising in both directions, then the mappings need to be unique in both directions to be resolved. For example, you can only map one type of SpecLog requirement to Product Backlog Items in TFS if you are synchronising from TFS to SpecLog as well. If multiple types of SpecLog requirements are mapped to PBIs, there is no way of back synchronising the PBIs, as the target SpecLog requirement type cannot be uniquely identified.
If you have previously been using V2 of the plugin, you should take care to follow the migration steps in the documentation before enabling V3. V3 uses a database table for synchronisation and this table is initialised with your current state when first migrating. This is important to ensure that previously synchronised requirements continue to be synchronised correctly.
More information on the V3 TFS plugin can be found here: https://github.com/techtalk/SpecLog-Resources/wiki/SpecLog.TFSPlugin.V3
-
Doug Snyder commented
This is a much needed request. Having a way to synchronize speclog in a way that supports the Epic\Feature\User Story hierarchy in TFS would make use of the speclog tool more efficient. Has their been any progress on making this capability a reality?
-
Jeremy Pridmore commented
I'd like to see this too. I am using the Agile template in TFS and would Ideally like to have:
1. the SpecLog Workspaces synchronised with my TFS Epics,
2. the SpecLog User Activities on those Workspaces created as Features and related to the appropriate Epic; and
3. the SpecLog User Stories created as TFS Stories and related to the appropriate Feature.
-
Mike commented
We also need a TFS type to map to User Actions because these are generally not User Stories either (it would be best if these too mapped to Features so that only genuine User Stories map to User Stories in TFS.
-
Attila Németh commented
Since the introduction of 'Agile Portfolio Management' in TFS 2013 (https://msdn.microsoft.com/en-us/library/dn306083.aspx) this would be essential, or you have to go without using 'Agile Portfolio Management' in TFS.