To track the evolution of your documents through the project lifecycle, you can create unique document versions at various stages of the project. You create the new version by checking in your document or content item. Creating a document or content version provides you with an exact record of the document as it was at the time you performed the check-in operation.

A live document is the originating document that is used to create a version (using a check-in operation). A live document and its contents can be changed throughout its lifecycle.

A document version represents the structure of the document and its contents at a specific point in its history. A content version is an artifact that represents a record of the content item at a specific point in its history. While a live document can continue to evolve, once a version is created, the significant content of that version cannot be changed.

Non-document model items cannot be versioned. Specifically, you cannot create versioned items from Test Steps or include them as part of versioned content.

Item revisioning adds a revision label to an existing item. Using the revision label, you can view the item historically as of that revision. Viewing is the only operation that can be performed on revisioned items. This is a light-weight solution to tracking the evolution of your items through the project lifecycle. Only non-document model items can use item revisioning, for example a Project or Release item type.

Document versioning records the document structure, creates new items, and adds a version label to the item being versioned (not the new items). You can view versioned items, add traces to versioned items, and modify certain fields on versioned items. In addition, you can also apply labels to versioned items, query for versioned items, chart versioned item data, and report on versioned item data. This is a more robust solution to tracking the evolution of your documents through the project lifecycle. Only document model items can use document versioning, for example, a Requirement Document (segment) and Requirement (node).

When you create a document or content version, the items that make up the original document or content (the live items) are copied to new items (the versioned items). Each created version has a unique identifier in the following format: Live Item ID-Major Version ID.Minor Version ID. For example, 7201-1.0, 7201-1.1, or 7201-2.0. A new version ID is displayed only when an item has been versioned. Live items continue to display item IDs with no version information, for example, 7201.

In the versioned items, basic fields and field values are copied from the live items. For example, integer, logical, and short text fields. For more complex fields, such as item backed picklist fields and query backed relationship fields. For more information, see Creating a Document Version.

One of the primary goals of document versioning is to make a copy of document content as of the time the content was versioned, preserving field values and document structure, thus allowing for the content to be queried and traced to.

To achieve the goal of traceability, some fields may need to be editable on versioned items. In particular, Relationship fields can be made editable; this allows tracing to versioned items or relating versioned items to project or release items. Picklist fields, Integer fields and Float fields can also be made editable; they can be used for storing metadata on versioned items. Note, however, that significant fields cannot be made editable regardless of their type.

Administrators can define which fields are editable on versioned items. Fields that are marked editable fields on versioned items must not also be marked as significant edit fields. In addition, fields marked as significant edit fields cannot also be marked as editable fields on versioned items. For additional information, see Trace Relationships in Content Versions.

In addition, you can query for versioned items, chart versioned item data, and report on versioned item data.

After checking in various document and content versions, you can include selected versions as part of a document baseline. For more information, see Baselining Documents.

A trace relationship is a special directional dependency that relates two documents or content items. For more information, see Trace Relationships in Content Versions.

To distinguish live documents from versioned documents in the GUI and Web interface, Integrity includes the following user interface components: