Skip to main content

skip to main content

developerWorks  >  Rational  >

IBM Rational ClearCase and IBM Rational ClearQuest Evaluation Guide, Part 1: Unified Change Management

An introduction to IBM's software change and configuration management solution

developerWorks
Go to the previous pagePage 2 of 8 Go to the next page

Document options
PDF format - Fits A4 and Letter

PDF - Fits A4 and Letter
61 KB

Get Adobe® Reader®


My developerWorks needs you!

Connect to your technical community


Rate this tutorial

Help us improve this content


Unified Change Management: Project lead role

You will start this evaluation in the role of the Project Lead. The project, organized by the Project Lead, is broken down into multiple components. Within those components are different required tasks. The basic tasks for this role include:

  • Logging on to the ClearQuest client
  • Running a query and viewing a distribution chart
  • Modifying a record and assigning a new owner for a defect

Log on and run a query

  1. In the ClearQuest perspective, click the ClearQuest menu and then click Login > Login.

Figure 1. Logging in to ClearQuest
graphic of log-in menu command

Figure 2. The ClearQuest Navigator
The ClearQuest Navigator

On the left, there is a menu of different queries available. You can use one of these or create your own custom queries to fit your needs.

  1. In the navigation pane, expand Public Queries > Classics PointOfSale Project > Submitted High Severity Defects.

Performing bug triage has never been easier. By running saved queries, the Project Lead can quickly identify which change requests or defects need immediate attention. And by looking at distribution charts, you can identify the workloads of your engineers and assign the defects to those that have the cycles to resolve them.

Viewing a chart of defects by owner

From the left-hand menu, you select Submitted High Severity Defects. These are the defects that have been submitted but not yet opened by Engineering. In the ClearQuest Query Results pane, you see that the defect report with the headline: Fix spelling error in Readme.html has yet to be assigned, that is, It is still in the Submitted state.


Figure 3. Chart of Defects by Priority by Owner
image of ClearQuest view showing distribution chart

Next, you run the query Distribution Charts > Defects by Priority > Owner which brings up a chart of the defects assigned to each engineer. You can use this information to decide to whom this defect can be assigned.

  1. Click on Public Queries > ClassicsPointOfSaleProject > Distribution Charts > Defects by Priority > Owner

On the chart shown in Figure 3, you see that team member Alex only has a few activities that are in the Opened or Assigned state, so you can assign this defect to Alex.

Modifying a record: Assign a new owner

Now that you have identified a developer to be the owner of the defect, you can modify the record and set the appropriate fields on the change request form. All the fields on a Rational ClearQuest form are completely customizable. You execute the Assign action and enter Alex as the Owner. You also set the Priority field and enter a note saying to further explain the change request. Once you've recorded all this information, you click Apply to update the record.

  1. In the Query results pane of ClearQuest Navigator (Figure 2), right-click on record CLSIC00000058, and click Change State > Assign.
  2. In the Modify...(record) dialog box, select the Main tab.
  3. Under Priority, select 1 - Resolve immediately.
  4. Under Owner, select alex.

Figure 4. Modify (record) dialog box - Main tab
image of Modify dialog box, showing selected fields
  1. Click the Notes tab.
  2. Under New Note, type some meaningful text for the new owner.
  3. Click in the Notes Log area to see you note added to this field.

Note: You can click the icon next to the New Note and Notes Log fields to bring up a text editor (Figure 5).


Figure 5. Modify (record) dialog box - Notes tab
image of Modify dialog box, showing selected fields

ClearQuest hooks can fire when an action is performed. One very important hook is the email notification hook. In this example, once the Modify action is complete, the notification hook could execute any Email Rules associated with the change request. For example, you may want the email rules set to watch for changes made to the Owner field and when the value changes, automatically generate and send email to the new owner informing them of the change.

  1. Click the Audit Trail tab.
  2. Verify that all the the audit information is captured in this record.
  3. Click OK to save your changes.

To meet regulatory compliance requirements, ClearQuest keeps a record of every action performed on a defect. The audit trail tab automatically keeps this information for the entire life of the defect.

Verify your changes and log out

You can now re-run the Defects by Priority > Owner chart and confirm that Alex now has ownership of the Submitted defect that you just modified.

  1. Click on Public Queries > ClassicsPointOfSaleProject > Distribution Charts > Defects by Priority > Owner
  2. Once you have confirmed your changes, click on the ClearQuest menu, select Database, and then click Disconnect.
  3. Logout of ClearQuest as user pat but remain in the ClearQuest perspective for the next section (where you will log back in as alex).
  4. Click OK to confirm your selections.

In summary, in this section we have seen how the Project Lead can:

  • Assess the project status and progress through standard and customized queries and charts.
  • Effectively allocate change requests to engineering resources.
  • Use customizable solutions or hooks to assign changes requests and automatically communicate project status to the team

Go to the previous pagePage 2 of 8 Go to the next page