A Baseline Definition is the filter criteria that is used to create a Baseline from a set of selected configuration items such as Tracker Artifacts, Documents, Source Code Repositories (only Git and Subversion are supported), File Releases, and Binaries (only Nexus binaries are supported) in a given TeamForge project.
Prerequisite: You must have Create/View Baseline permission to both create and view Baseline Definitions. You need View Only permission to only view Baseline Definitions.

Create Baseline Definitions

You can create Baseline Definitions from either the Create Definition page or a Create Baseline page.

Create Baseline Definition from Create Definition Page

  1. Log on to TeamForge and select a project from My Workspace.

  2. Click Baselines from the Project Home menu. The Baselines list view is shown by default.

  3. Click Definitions from the side navigation menu.

  4. Click New Definition on the Definitions list view.

  5. Enter values for the required fields on the Create Definition page.

  6. Select one or more Baseline Definitions from the Include Definitions drop-down list. Click the selected Baseline Definition to view it.

    You can search for the Baseline Definitions that are not listed in the Include Definitions drop-down list. Only two selected Baseline Definitions can be shown at a time. To see the complete list of selected Baseline Definitions, click + More in the Include Definitions drop-down list.

  7. Define the filter criteria.

    You can define the filter criteria for Trackers, Documents, Source Code Repositories, File Releases and Binaries. Select the following tabs to view instructions.

    1. Select the tracker type(s) from the Tracker Type drop-down list.
    2. Click Add Filter(s).
      • Attribute–Select a tracker attribute from the drop-down list.
      • Condition–Select a condition from the drop-down list.
      • Value–For the selected attribute, either select one or more values or enter a value.

      For example, the following filter includes all the Closed tracker artifacts in the baseline.

    3. Click Add “AND” Condition to add more constraints to the filter criteria.
    4. Repeat steps b and c to add more filters.

      You can click the remove icon ( ) next to a filter criteria to remove it.

    5. Select the planning folder. Selecting the parent/root planning folder shows all its child/sub folders.

      For folders with sub folders, click More to view the complete folder structure and select the required folders.

      To view the filtered list of artifacts, click the view icon ( ) in the TRACKER/PLANNING FOLDER section. The Tracker/PlanningFolder Preview dialog box appears.

      You can also do a keyword search by clicking the search icon ( ) on the Tracker/PlanningFolder Preview dialog box.

    1. Select the document folder.

      For folders with sub folders, click More to view the complete folder structure and select the required sub folders.

    2. Select the document version.
    3. Click Add Filter(s).
      • Attribute–Select an attribute from the drop-down list.
      • Condition–Select a condition from the drop-down list.
      • Value–For the selected attribute, either select one or more values or enter a value.
    4. Click Add “AND” Condition to add more constraints to the filter criteria.
    5. Repeat steps c and d to add more filters.

      You can click the remove icon ( ) next to a filter criteria to remove it.

      To view the filtered list of documents, click the view icon ( ) in the DOCUMENTS section. The Documents Preview dialog box appears.

      You can also do a keyword search by clicking the search icon ( ) on the Documents Preview dialog box.

    1. Select a repository from the Repository/Source Name drop-down list. Select the repository again if you want to clear your selection.

    2. Select a tag for the selected repository. Select the tag again if you want to clear your selection.

      Tagging is one of the features of version control systems that lets you mark particular revisions (for example, a release version)—so that you can recreate a certain build or environment at a later point in time.

      • The Select Tag drop-down list shows all the tags you have for the selected Git or Subversion repository.
      • For Subversion repositories, the list of tags comes from the /tags directory of the repository.
      • For more information about SVN tags, see Branching / Tagging.
      • You can click the View Tag link to view the tag details.
    3. Click Add another Repository to add more repositories.

    Select the package or the release name from the Package/Release Name drop-down list.

    To view the filtered list of files, click the view icon ( ) in the File Releases section.

    You can also do a keyword search by clicking the search icon ( ) on the File Releases dialog box.

    Select the server name or repository name from the Server/Repository Name drop-down list. All the folders, subfolders and files in the repository are selected by default.

    For repositories with sub folders, click More to view the complete folder structure and select the desired folders/files.

  8. Select one or more external baselines from the External Baselines drop-down list.

    Click the selected External Baseline to view it.

    You can search for the External Baselines that are not listed in the External Baselines drop-down list. Only two selected External Baselines can be shown at a time. To see the complete list of External Baselines, click + More in the External Baselines drop-down list.

  9. Click Create Definition.

Once created, the new Baseline Definition is added to the list of Baseline Definitions.

Create Baseline Definition from Create Baseline Page

  1. Log on to TeamForge and select a project from My Workspace.

  2. Click Baselines from the Project Home menu. The Baselines list view is shown by default.

  3. Click New Baseline on the baseline list view.

  4. Enter values for the required fields.
  5. Define the filter criteria.

    You can define the filter criteria for Trackers, Documents, Source Code Repositories, File Releases and Binaries. Select the following tabs to view instructions.

    1. Select the tracker type(s) from the Tracker Type drop-down list.
    2. Click Add Filter(s).
      • Attribute–Select a tracker attribute from the drop-down list.
      • Condition–Select a condition from the drop-down list.
      • Value–For the selected attribute, either select one or more values or enter a value.

      For example, the following filter includes all the Closed tracker artifacts in the baseline.

    3. Click Add “AND” Condition to add more constraints to the filter criteria.
    4. Repeat steps b and c to add more filters.

      You can click the remove icon ( ) next to a filter criteria to remove it.

    5. Select the planning folder. Selecting the parent/root planning folder shows all its child/sub folders.

      For folders with sub folders, click More to view the complete folder structure and select the required folders.

      To view the filtered list of artifacts, click the view icon ( ) in the TRACKER/PLANNING FOLDER section. The Tracker/PlanningFolder Preview dialog box appears.

      You can also do a keyword search by clicking the search icon ( ) on the Tracker/PlanningFolder Preview dialog box.

    1. Select the document folder.

      For folders with sub folders, click More to view the complete folder structure and select the required sub folders.

    2. Select the document version.
    3. Click Add Filter(s).
      • Attribute–Select an attribute from the drop-down list.
      • Condition–Select a condition from the drop-down list.
      • Value–For the selected attribute, either select one or more values or enter a value.
    4. Click Add “AND” Condition to add more constraints to the filter criteria.
    5. Repeat steps c and d to add more filters.

      You can click the remove icon ( ) next to a filter criteria to remove it.

      To view the filtered list of documents, click the view icon ( ) in the DOCUMENTS section. The Documents Preview dialog box appears.

      You can also do a keyword search by clicking the search icon ( ) on the Documents Preview dialog box.

    1. Select a repository from the Repository/Source Name drop-down list. Select the repository again if you want to clear your selection.

    2. Select a tag for the selected repository. Select the tag again if you want to clear your selection.

      Tagging is one of the features of version control systems that lets you mark particular revisions (for example, a release version)—so that you can recreate a certain build or environment at a later point in time.

      • The Select Tag drop-down list shows all the tags you have for the selected Git or Subversion repository.
      • For Subversion repositories, the list of tags comes from the /tags directory of the repository.
      • For more information about SVN tags, see Branching / Tagging.
      • You can click the View Tag link to view the tag details.
    3. Click Add another Repository to add more repositories.

    Select the package or the release name from the Package/Release Name drop-down list.

    To view the filtered list of files, click the view icon ( ) in the File Releases section.

    You can also do a keyword search by clicking the search icon ( ) on the File Releases dialog box.

    Select the server name or repository name from the Server/Repository Name drop-down list. All the folders, subfolders and files in the repository are selected by default.

    For repositories with sub folders, click More to view the complete folder structure and select the desired folders/files.

  6. Select one or more External Baselines from the External Baselines drop-down list.

    Click the selected External Baseline to view it.

    You can search for the External Baselines that are not listed in the External Baselines drop-down list. Only two selected External Baselines can be shown at a time. To see the complete list of External Baselines, click + More in the External Baselines drop-down list.

  7. Click Preview to Create to preview the Baseline Definition.

    Preview Baseline

  8. Click Save as Definition to save the Baseline Definition.

  9. Either enter a new name for the Baseline Definition or leave the Baseline title in the Name field.

  10. Click Save. If the entered name already exists, you are prompted to enter a different name.


    Once saved, the new Baseline Definition is added to the list of Baseline Definitions.

  11. If required, click Back to edit the Baseline Definition on the Create Baseline page.

Create Baseline Definition from an Existing Baseline Definition

You can create an Baseline Definition using an already existing Baseline Definition from the Create Baseline page.

Create Baseline Definition from Create Baseline Page

Instead of creating an Baseline Definition from the ground up, you can build one from an already existing Baseline Definition.

  1. Repeat steps 1 through 4 as discussed earlier in Create Baseline Definition from Create Baseline Page.

  2. Select a Baseline Definition from the Definition drop-down list. The selected Baseline Definition’s filter criteria are auto-populated.

  3. Review the filter criteria and modify the filters, if required.

  4. Repeat steps 5 through 10 as discussed earlier in Create Baseline Definition from Create Baseline Page and create the new Baseline Definition.

    Once saved, the new Baseline Definition is added to the list of Baseline Definitions.

View Baseline Definition

  1. Log on to TeamForge and select a project from My Workspace.

  2. Click Baselines from the Project Home menu.

  3. Click Definitions from the side navigation menu.

  4. Select a Baseline Definition from the list to view its details.

    View Baseline Definition

Delete Baseline Definition

You can delete a baseline definition as long as you have the DELETE/VIEW BASELINE DEFINITION permission assigned to you. Existing baselines, if any, created from deleted baseline definitions, are not affected in any way.

Users with the DELETE/VIEW BASELINE DEFINITION permission can:

  • Search for baseline definitions
  • View baseline definitions
  • Delete baseline definitions

You can delete baseline definitions—only on a case-by-case basis—from the View Baseline Definition page.

To delete a baseline definition:

  1. Select a baseline definition to view it.
  2. Click the Delete icon on the View Baseline Definition page.

    Delete icon to delete the baseline definition
  3. A confirmation message appears.

    The reason for deleting the baseline definition
  4. You must type a reason to delete the baseline definition and click Yes, I’m sure. The comment/reason you type is stored in the database and is associated with the baseline definition you are trying to delete.

    The baseline definition is deleted.

An email notification is sent to the user that created the baseline definition.