Add a new release (see Creating or copying a release). Select the process to be used for the new release, and then select the baseline release for the new release.
During the development cycle, some tasks are not included for the current release. One reason that tasks are not included is because the tasks were not completed. To bring in the tasks after they are completed during your new release, update the release value for the tasks. Update then sees the tasks as candidates to be included in your project configuration.
Rational Change Users:
OR
Rational Synergy Users:
Click Find > Tasks
In the Query dialog box, enter the following custom query. The following query returns all completed tasks for the given release (task_release) that are not in the latest baseline with the given release (baseline_release) and purpose (baseline_purpose).
is_available_task_of_release(task_release, baseline_release, baseline_purpose)
Further, the latest baseline is selected from all baselines in the test_baseline, published_baseline or released state. For a task to be considered to be in a baseline, it must be included in the update properties of all projects making up that baseline.
The result of the query shows tasks that were completed after the final build for the release, and were incorrectly left tagged for the release. (Tag these tasks for the new release.)
If the project contains subprojects, the release is copied automatically to the subprojects.
Developers must change the release value for the project hierarchy.