In this lesson, you will learn how to create an iteration
type, apply it to an iteration, and customize behavior for the iteration
type.
About this task
An iteration type is a way of categorizing iterations. After
you create an iteration type, you can specify that an iteration belongs
to that iteration type. You can customize the project area to specify
permission settings and operation behavior for an iteration type.
When the current iteration belongs to an iteration type, the permission
settings and operation behavior for that iteration type are used.In
this lesson, you will create an iteration type named Stabilization,
which the development team will use during the final iterations of
a release. To ensure that developers do not introduce defects late
in the release, you will set a precondition on the Deliver operation
that requires the developer to get an approval on the work item associated
with their change set.
To create an iteration type and customize
behavior for it:
Procedure
- If you are not already logged on to the web client as Bert,
log on now. Navigate to the Customization Tutorial Project
(Change Management) project area. Click Iteration
Types. Click , the Create a New
Iteration Type icon. Enter a name, such as Stabilization,
and identifier for the iteration type. Click Save.
- Click Timelines. Within the Main
Development timeline, expand the Release 1.0 iteration
and select the Sprint 1 iteration. Notice that
this iteration has , the Current
Iteration icon. Click Edit Properties.
In the Iteration Type field, select Stabilization.
Click OK. Click Save to
save your changes to the project area.
- In the IBM® Engineering Workflow
Management client
for Eclipse IDE, log out as Hal. Log on as Bert.
- In the project area, click the Process Configuration tab.
Expand .
Select Operation Behavior.
Click in the
Deliver (client) cell
for the
Intern role. Select
Preconditions
and follow-up actions are configured for this operation.
Click
Add. In the Add Preconditions window,
select both
Require Work Item Approval and
Require
Work Items and Comments. Click
OK.
Select
Require Work Item Approval in the
Preconditons list.
In the
Required approvals section,
click
New. In the New Required Approvals window,
specify that one approval from someone with the
Product
Owner role is required. Click
OK.
Click
Save.
- Log out. Log on as Hal. In the Navigator view.
double-click the readme.txt file that you created previously to open
it. Make a change, then close and save the file. In the Pending
Changes view, expand the Unresolved folder
to see the change set. Right-click Unresolved and
select Check-in all. Expand the Outgoing folder.
Right-click Enter a comment and select . Select the work item that you created
for your previous delivery. Make a note of the work item number. Click OK.
Right-click the change set and select Deliver.
The following message is displayed in the Team Advisor view.
- Enter the work item number in the work item search field
at the bottom of the window.
Click Enter to open
the work item. Click the Approvals tab. Click New
Approval. Click Add Approver. Add
Bert. Click OK. Click Save to
save the work item.
- Log out. Log on as Bert. In the work item, click in the State column
for the approval and select Approved. Click Save.
- Log out. Log on as Hal. In the Pending Changes view,
try to deliver the change set again. Now the operation succeeds.