Managing the team with work items

You can use work items to manage your work and to manage the work of your team.

With the Jazz-based work item system, team members can assign tasks and defects to each other and view everyone's status. Test plan authors and test case designers can distribute their work for review and track the status of each reviewer. Test cases can be linked to development work items to better track the progress of product features.

Prior to version 3, work items were managed locally within the tool itself or in an external defect provider, such as IBM® Rational® Team Concert™ or Rational ClearQuest®. In version 4, by default, work items are no longer managed locally. Rather, they are managed in the external defect provider.

If you use the Change and Configuration Management (CCM) application of Rational Team Concert as your defect provider, you can view the remote work item in an embedded tab within Rational Quality Manager. The My Tasks widget will be updated accordingly to show the remote work items and defects. Bidirectional links are also created automatically for traceability and navigation. As a result, you can easily navigate to the work item from Rational Quality Manager and also navigate to test artifacts from the Change and Configuration Management work item.

Predefined work item types

The following table lists and describes work item types and explains how they are represented in different versions of Rational Quality Manager.

Work item type Description
Requirement An externally stored requirement work item. Starting in version 3, Rational Quality Manager no longer uses the local work item system to store any type of requirement. All requirements, except the proxies for requirements imported from Rational DOORS®, are requirement references to Requirements Management (RM). The proxies for Rational DOORS are stored locally in the quality management (QM) database as modeled objects (not work items).
Defect An externally stored work item used to track a defect in the application under test. Starting in version 3, new Defect work items are stored by your Change and Configuration Management (CCM) provider. Defect work items migrated from version 2 are stored locally. However, the migration sets up Rational Quality Manager so that it appears as just another CCM application. Therefore, you access local work items the same way that you access work items stored by any other CCM provider.
Task-Quality An externally stored work assignment that is typically associated with a test plan, test case, or test script. For example, when a user is asked to complete a section of a test plan, that user is assigned a Task-Quality work item. Starting in version 3, new Task-Quality work items are stored by your Change and Configuration Management (CCM) provider. Task-Quality work items that are migrated from version 2 are stored locally and accessed the same way as migrated Defect work items.

In version 3, any new requirements that you create are created in the Requirements Management (RM) application that can be installed with the product. It is recommended that you create Defect and Task-Quality work items in the Change and Configuration Management (CCM) application or another external CCM provider.

Note: Using a project area that has been migrated from version 3, it is still possible to create and manage Task-Quality work items within the tool, but to take full advantage of lifecycle integrations, it is highly recommended that you create and manage new work items in the Change and Configuration Management application.

video icon Watch videos

CLM playlist
Jazz.net channel
User Education channel

learn icon Learn more

CLM learning circle
Agile learning circle
Learning circles

ask icon Ask questions

Jazz.net forum
developerWorks forums

support icon Get support

Support Portal
Deployment wiki
Support blog