16 docs tagged with "baseline"

As a baseline administrator, you can configure the custom attributes used in the baselines, configure the custom statuses, and manage workflow status transitions and field inclusions.

You can compare two Baselines created at two different points in time to know the differences. You can also compare the Baseline Definitions of two Baselines.

Create a Baseline when you accomplish specific milestones in your project or when you release or deliver a product. You can create a Baseline from either a Baseline Definition or from the ground up.

A Project Baseline is a baseline created on a project at a given point in time. Once you have Project Baselines created, you can kick start new projects from Project Baselines and proceed from when and where the Project Baselines were created in the past. Project Baselines are typically created using Project Baseline Definitions, when you release or deliver a product. You can create as many Project Baselines as required.

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.

You can delete Open and Rejected (meta status) baselines as long as you have the DELETE/VIEW BASELINE permission assigned to you. You cannot delete approved baselines.

You can edit an existing Baseline Definition to add more filter criteria or modify the existing fields and filter criteria.

You can edit the existing fields in a Baseline as long as the Baseline is in open status. A Baseline cannot be edited after it is approved or rejected.

You can enable caching for TeamForge Baselines in case you have a large number of binary (Nexus) repositories. Caching Nexus repositories enables fast loading of Nexus repositories when you try to create or modify the binary filter criteria for baselines or baseline definitions.

You can generate a downloadable package of physical project artifacts such as Tracker Artifacts, Documents, Source Code Repositories (only Git and Subversion are supported), File Releases, and Binaries (only Nexus binaries are supported) from an approved Baseline or a Project Baseline and share the package with your stakeholders.

Baseline

Here's what it takes to install and run TeamForge and other integrations supported by TeamForge.

A Project Baseline Definition is the filter criteria that is used to create a baseline from a set of selected configuration items at the project level.

A Baseline or a Project Baseline, once created can be reviewed. During the review cycle, the Baseline or the Project Baseline undergoes various status transitions as defined by the Baseline Administrator.

You can search for the existing Baselines, Project Baselines and Baseline Definitions based on all stored attributes.

What is a Baseline Definition?