Configuration Management Project Differences View

The Project Differences view displays project differences between checkpoints of project. The changes to a project and its members are not tracked as they happen, but rather the View Project Differences command takes two checkpoints (or one checkpoint and the current version) and then compares them.

The By Member panel displays the following information:

• Name displays name of the project, subproject, or member changed.

• Change displays the operation performed on the member or subproject, and the resulting revision number.

Selecting a member entry displays the following information:

• Date displays the date each revision in the history was created.

• C.P. ID displays the revision’s associated change package ID.

Members that were checked in between the two checkpoints without updating the revision number do not appear in the Project Differences view, and do not display change package information in the By Change Package panel.

Change package information displayed on the By Change Package panel is drawn from the modifications calculated from the checkpoint comparison.

The By Change Package panel displays the following information:

• ID displays the change package ID for change packages that contain entries with member changes between project checkpoints.

• Summary displays the change package summary for change packages that contain entries with member changes between project checkpoints.

Modifications that are not associated with a change package (unresolved) are displayed in the bottom frame of the By Change Package panel. Where possible, the member or project name displays with full path information.

The By Change Package panel does not show which change packages have been propagated between project checkpoints on different branches.

The following are reasons why modifications can appear in the bottom frame:

• The change package entry is missing, either because one was not recorded for the member operation or the entry was discarded.

• The operation that made the modification cannot use a change package, for example, adding a subproject.

• The project state captures compared are from different development paths.

Pending change package entries do not appear in the By Change Package panel.