By clicking on the button New a a new empty table row will appear. Now, Name, Start Date and Due Date can be defined.

With Save the new iteration is created and saved. The ID of the iteration (ITR00001) is automatically assigned by Klaros-Test­management. Click on the ID ITR00001 to get to the detail page of the iteration.

With New several table rows can be created and edited at the same time. Only when clicking on Save the data is stored in the database.

	Red IDs
	All rows with red IDs have been changed and are not yet saved!

With Discard all changes are undone.

The following actions can be performed in the action column:

If an iteration has been deleted, it is initially marked with a deletion marker and is only visible to administrators. For deleted iterations, the following actions are available instead of Delete:

On the Iterations page, one or more iterations can be selected for bulk actions. Bulk actions are described in Section 5.2.3.1.5, “Bulk Actions”.

The following bulk actions are supported for iterations:

Bulk actions are described in detail in Section 5.2.3.1.5, “Bulk Actions”

The following operations can be performed in the line above the table on the right:

All operations are described in detail in Section 5.2.3.1, “Overview Page”.

To quickly switch between iterations, a quick selection is also available in the page header (see Figure 6.14, “Quick Selection of Projects and Iterations”).

Figure 6.14. Quick Selection of Projects and Iterations

When an iteration is active, only test objects relevant to the test cycle represented by the iteration are visible. If a test run is executed while an iteration is active it will be linked to the iteration automatically. This helps to separate the test results of a given test cycle from other activity.

All data displayed here always refer to the currently displayed iteration.

The following values are displayed on the overview tab:

Figure 6.16. The Iteration Success Rate

Figure 6.17. The Iteration Radar Chart

	Note
	All test cases that are part of the iteration (via requirements) contribute to the metrics of this tab. If none are explicitly registered for this iteration, then all test cases of the project are considered.

This tab ( Figure 6.18) allows the user to view or change the following attributes of the iteration:

Figure 6.18. The “Properties” Tab - Iterations

You can create your own fields to meet individual requirements. For further information please refer to Section 5.2.3.2.4, “User Defined Properties”.

You can add any files as attachments to an iteration. For more information, see Section 5.2.3.2.6, “Attachments”.

If you want to associate test environments with the iteration, click the Assign button and select one or more test environments.

The page lists all systems under test assigned to the iteration, with their respective states:

* Only present if at least one requirement is associated with the iteration.

If you want to associate systems under test with the iteration, click the Assign button and select one or more test environments.

The Requirements tab shows the requirements which have been assigned to this iteration, as well as their Compliance and Coverage rates. These metrics refer to the test cases linked with the requirements and the last results of these executions. The following values are displayed:

If you want to associate requirements with the iteration, click the Assign button and select one or more requirements.

The page displays a list of jobs assigned to the selected iteration.

The following values are displayed in the table:

The results tab is further divided into a Test Runs, Test Case Results and a Test Suite Results tab, showing the test results related to this iteration as described in Section 5.2.3.2.7, “Test Runs and Results”.

The tab Changes shows the change history of this iteration.

For a detailed description of the Changes view, see Section 5.2.3.2.8, “Change History”.