When a project creates a specific baseline definition, it is not possible to share this to other projects via export/import
It would be great when TF allows to export a baseline definition, and to import a baseline definition in another project

by: Rudolf W. | over a year ago | Baselines

Comments

• The challenge here is that the baseline definitions implicitly contains custom attributes and selected values (for Trackers, Documents, etc.) as part of the inclusion criteria which may differ from one project to another. Hence exporting definitions from one project and importing them into another is not feasible.

  by: Govind P. | over a year ago

• Thank you for the explanation, Govind.
  But I wonder that you see this as a challange.
  When the system imports the baseline definition, it checks if the attribute names and selected values exist in the data model of the target project, and filters this out from the new baseline definition.
  It warns the user about the filtering. I cannot see why this is not feasible.

  by: Rudolf W. | over a year ago