This information is for planning purposes only. The information herein is subject to change or removal without notice before the products described may become available.
The CE/CLM products were renamed in version 7.0. As the help is updated to reflect the changes, the topics might contain inconsistencies. For details on the name change, see Renaming the IBM Continuous Engineering Portfolio.

Setting up timelines, iterations, and team areas

The Quality Management (QM) application integrates with the timelines, iterations, and team areas features of Jazz® Foundation. When you create a test schedule in a test plan, you associate the schedule with a timeline and its iterations.

Before you begin

To create and modify timelines and iterations you must belong to a role that is assigned  the Modify the iteration structure permission. See Role-based permissions that are common to all Collaborative Lifecycle Management applications.

About this task

The first step in using timelines is to define a set of iterations for your project area in your project timeline. At the time of project area creation, a timeline is automatically created and set as the project timeline. A timeline specifies how a given planned period of time can be partitioned into smaller units of time called iterations. Typically, you create a hierarchy of iterations, where the top-level iteration represents a release and the child iterations represent milestones within the release.

By default, the project timeline is the only timeline that is enabled in the QM application. Each timeline has a current iteration that controls the process behavior. The current iteration can be useful because it allows you to define generic execution record queries by leveraging the Current Iteration filter value. It also allows you to implement point-in-time governance. For further details about these concepts, see Timelines and Iterations® in Rational® Quality Manager.

You can define additional timelines and iterations in the timeline editor. For example, if you work on a project that involves both new product development and current product maintenance, you can define separate timelines for each of these efforts. You can also define timelines to use with different team areas. For example, you can create one timeline for the functional test team, and another timeline for the system verification test team.

As of version 4, you can subdivide your project areas into smaller teams and assign different permissions to user roles within each team. Users must be members of the team to perform team-level operations. You define team areas on the Overview tab of project area administration. Typically, you assign a timeline and a set of iterations for the team area to use.

You can access the timeline and iterations editor by clicking the Administration (Administration) icon in the upper-right portion of the banner and selecting Manage Project Timelines.


  1. Decide which timelines are needed for the project area. You can use the default project area timeline or create additional timelines.
  2. Optional: Enable team areas and support for multiple timelines.
  3. Optional: Create additional timelines.

  4. Create iterations for each timeline.

    Typically, you create a hierarchy of iterations, where the top-level iteration represents a release and the child iterations represent milestones within the release. The following figure shows a project area that is organized into multiple timelines and iterations:

    timelines editor

    This figure shows three timelines: Main Development Line, Maintenance Timeline, and the FVT Team Timeline

    The Main Development Line [Project Timeline] includes two release-level iterations - (4.0 and 5.0) and several milestone-level iterations. The Maintenance timeline includes one release-level iteration (4.0) and one milestone-level iteration (M1). The FVT Team Timeline includes one release-level iteration (4.0) and two milestone-level iteration (M1 and M2).

    When you create an iteration, set the iteration so that a test plan can consume it. In the Edit the Iteration window, click A release is scheduled for this iteration.

    Edit the iteration dialog box
  5. Optional: Define team areas and associate each one with a timeline.
  6. Open or create a test plan.
  7. Optional: Select a team area for the test plan.
  8. Define the test plan schedule by associating the test plan with a set of iterations.

video icon Video channel
Software Education channel

learn icon Courses

IoT Academy
Skills Gateway

ask icon Community forums library

support icon Support

IBM Support Community
Deployment wiki