OnRoad Test Management

Thanks - that works great!

Now one more question please.

Currently we use your BackupUtility.exe v2.0.3530.26622

Do we have to upgrade the BackupUtility.exe as well?

Are there any other things that need upgrading?

Once again thanks for your support.

Yes - all those utilities are on the same version as the sync services.

//Ilpo

When I run the BackupUtility.exe v2.2 i get the following output:

C:\Program Files\Juvander Consulting Oy\TFS Bug Item Synchronizer for Quality Ce
nter\Backup>BackupUtility.exe 4040 "C:\Program Files\Juvander Consulting Oy\TFS
Bug Item Synchronizer for Quality Center\Backup\Files\erroryapfile.yap"
Copying 430872 items
Contains also DataLibrary.DefectMessageClass+MessageDirection
Contains also DataLibrary.ProjectMapType
Contains also DataLibrary.DefectClass+SourceSystemEnum
Contains also DataLibrary.WorkItemClass+SourceSystemEnum
Contains also DataLibrary.LicenseInfoClass
Contains also DataLibrary.QCProjectDefinitionClass
Done 7398 items

Does that look OK?

Thank you!

Yes, this is ok.

//Ilpo

Now we have the following synchronization scenario which works fine (using the DestinationWorkItemTypeValueMap):

1. QC-Item: Defect ("Type = Defect") <-> TFS-Item: Bug
2. QC-Item: Defect ("Type = Change Request") <-> TFS-Item: Change Request

Question:
Is the following scenario somehow possible (one way only sync of Change Requests) :
1. QC-Item: Defect ("Type = Defect") <-> TFS-Item: Bug
2. QC-Item: Defect ("Type = Change Request")  -> TFS-Item: Change Request

Thank you!

For now only way would be to define ErrorDB field in your TFS project and no Destination Project. Then in case Change Request clear this field.

Will make a note on this for the future.

//Ilpo

1. "In case Change Request clear this field "  - Do you mean this choice field: TFS Projects -> TFS Project WorkItem Types (selecting only "Bug" instead of "Bug", "Change Request")?

2. What do you mean "define ErrorDB field" ? I can see the ErrorDB field under TFS Projects - but what should be defined there (currently the value of this field is "(Not defined)"?

Thank you!

What I meant was that if you have ErrorDB field defined in your TFS project sync settings and no Destination Project, only those new workitems will be sent to QC which have value in ErrorDB field.

This field should have value in format of QCDOMAIN.QCPROJECT, exactly like you configured your QC projects. It is case sensitive.

//Ilpo

We currently have the following synchronization scenario, which works fine:

1. QC-Item: Defect ("Type = Defect") <-> TFS-Item: Bug
2. QC-Item: Defect ("Type = Change Request")  -> TFS-Item: Change Request

In the QC Projects settings -> "Filter Field Value" we have the following entry: "Open or Closed or Assigned or Clarification".

Now the question:

Is it somehow possible to define different values for "Filter Field Value" for the two QC Items?

E.g.:

1. Synchronize QC-Item: Defect ("Type = Defect") when Status = "Open or Closed or Assigned or Clarification"

2. Synchronize QC-Item: Defect ("Type = Change Request") when Status = "Open"

Thank you!

From QC project settings in sync admin not.

But if you build an workflow to change ErrorDBSyncStatus according to these rules then it is possible to it in there.

//Ilpo

When upgragding from v2.1 to v2.2 - can I skip the "Install Services" section?

Because I already have the Services installed

Thank you.

Actually, these services will be uninstalled when you uninstall previous version. So first uninstall main setup and then components setup and then install again.

This install services -option is there since on some systems it fails to install services during installation and they are then manually installed afterwards using the provided .cmd file.

//Ilpo

On the machines here the uninstall does not work. There is no entry "TFS Bug Item Synchronizer" in the Add/Remove Programs section.

And because I cannot uninstall I get errors when installing the Services because the old Services are still there.

So - in my special case - can I skip the "Install services" section?

Thank you!

Yes, you can use it for that as well.

//Ilpo

I upgraded two different machines with v2.2

Now I noticed a difference in the TFStoTDFieldMapping.xml

The first machine shows:

<FIELDMAPPING Name="">
    <FIELD VALUEMAPNAME="">
      <FIELDDATAMASTER>None</FIELDDATAMASTER>
      <HTMLFORMAT>False</HTMLFORMAT>
      <FIELDMETHOD>OnUpdate</FIELDMETHOD>
      <RESOLVEUSERNAME>False</RESOLVEUSERNAME>
      <TDFIELD FieldTechnicalName="BG_SUMMARY" FieldLabel="Summary">BG_SUMMARY</TDFIELD>
      <TFSFIELD FieldTechnicalName="System.Title" FieldLabel="Title">Title</TFSFIELD>
      <DEFAULTVALUE />
      <FORCEFIELDUPDATE>False</FORCEFIELDUPDATE>
    </FIELD>

The second shows:

<FIELDMAPPING Name="">
    <FIELD VALUEMAPNAME="">
      <FIELDDATAMASTER>None</FIELDDATAMASTER>
      <HTMLFORMAT>False</HTMLFORMAT>
      <FIELDMETHOD>OnUpdate</FIELDMETHOD>
      <RESOLVEUSERNAME>False</RESOLVEUSERNAME>
      <TDFIELD>BG_SUMMARY</TDFIELD>
      <TFSFIELD>Title</TFSFIELD>
      <DEFAULTVALUE />
      <FORCEFIELDUPDATE>False</FORCEFIELDUPDATE>
    </FIELD>

In the Synch-Admin-Tool both look the same - but on xml level there is this difference.

Do you have an explanation for that?

Thank you!