Search
Recent Entries
DotNetNuke Blog Enhancements
Released: OffRoad 2.9 for HP Quality Center
BETA OffRoad 2.9 for HP Quality Center is available
BETA TFS Bug Item Synchronizer 2.6 available
Migrating from Community Server to Dotnetnuke
Released Import Export Utility 2.0 for Quality Center
TFS Bug Item Synchronizer, new coming features
By Ilpo Juvander on 1/31/2010 10:37 AM
Next major version of popular TFS Bug Item Synchronizer for Quality Center is now released.

TFS Bug Item Synchronizer is an tool which allows testing and development teams to work together using tools built for their usage. Testers enter defects in Quality Center and when defect is created and updated into TFS, developer can fix it, link all changes to it and mark it as fixed. After this the tester will continue process on Quality Center side to verify the fix. Similar to this developer can create a work item and have it synchronized over to Quality Center for testers to verify the fix.

With this tool it is possible to synchronize both Quality Center Defects and Requirements with TFS work items.

Testers will only need to use Quality Center and developers TFS, no need to have both applications on both teams as this tool works totally on the server side.

This version supports

Quality Center 10.0 Quality Center 9.2  Quality Center 9.0 Quality Center 8.2 TestDirector...
By Ilpo Juvander on 1/12/2010 10:01 AM
We have again listened to Your valuable input on what new features there should be on TFS Bug Item Synchronizer. So keep these coming in towards us through our support.

We are now almost done with the next TFS Bug Item Synchronizer version.

Here’ some of the highlights on what will be in it:

Support for multiple TFS servers, mainly due to getting ready for TFS2010 version but current TFS2008 and TFS2005 will also benefit from this Support for QC10 with version control enabled for requirements Added possibility to combine fields from QC into TFS field. This is implemented so that QC field is left as undefined and default value for field contains QC fields in following format (this is from requirement): #RQ_REQ_ID# #RQ_REQ_NAME# RequirementType #RQ_TYPE_ID#. So this can include fields which are replaced when updating and also fixed values New UI for setting properties:...
Copyright 2011-2013 by Juvander Consulting Oy