No | Feature | IBM Rational ClearQuest Package
| CM-Consult's ProjectTracker 2.5.0 |
Configuration |
| 1 | Necessity to use the special ClearQuest package to ensure the possibility of integration. | Yes. For CRs that should be imported into the plan, it is necessary to apply the ClearQuest packages: AMBaseActivity, AMWorkActivitySchedule. | No. ClearQuest packages are not necessary for integration. The module is compatible with the following packages: AMBaseActivity, AMWorkActivitySchedule. |
| 2 | Configuring compliance of main fields in MS Project plan and the ClearQuest CR: headline, owner, planned and actual dates. | Yes. Exact configuration of compliance with fields of the ClearQuest package only. | Yes. Flexible configuration of compliance with any fields. |
| 3 | Configuring work with several types of CRs. Allows creating different types of planned work: planning tasks, planning work on defects and requests, etc. | Yes. Only with those CRs for which compliance with ClearQuest packages is configured. | Yes. Any CRs, and any stateless record types. |
| 4 | Configuring compliance of additional fields in MS Project plan and the ClearQuesr CR. Allows importing and synchronizing CR fields, that are not related to planned and actual dates, for example, priority, importance, system, subsystem. | Yes. | Yes. |
| 5 | Configuring compliance of additional fields-references in MS Project plan and the ClearQuesr CR. Allows importing and synchronizing CR fields, that represent references to other CRs or stateless record types, for example, system, subsystem. | No. | Yes. |
| 6 | Configuring automatic import of values from a list for fields into an additional field basing on configured dynamic ClearQuest lists. | Yes. | Yes. |
| 7 | Configuring automatic importing of values from a list for fields into an additional field basing on the ClearQuest CR. Allows generating a value list basing on CRs or stateless record types. | No. | Yes. |
| 8 | Configuring automatic importing of users into the MS Project plan. Allows maintaining an up-to-date user list. | No. | Yes. Allows configuring user import for both all users, and the defined project. |
| 9 | Configuring functioning of hierarchical relations within one CR. Configuring relations of the Task-Task type. | Yes. | Yes. |
| 10 | Configuring functioning of hierarchical relations within several CRs. Configuring relations of the Request-Task type. | Yes. | Yes. |
| 11 | Configuring combination of hierarchical relations within several CRs. Configuring relations of the Request-Task-Task type. | No. | Yes. |
| 12 | Configuring dependencies between tasks. | No. | Yes. |
| 13 | Configuring calculation of work effort. Allows performing selective importing of actual completion rate: in percentage, or in hours. | No. | Yes. |
Importing from ClearQuest |
14 | Manual task importing. A form opens, where tasks for importing are selected. | Yes. | Yes. |
15 | Automatic task importing. Based on configured query, that automatically generates a list of tasks for importing. | No. | Yes. |
16 | Hierarchical task importing. Tasks and subtasks are generated automatically. | Yes. | Yes. |
17 | Automatic importing of child tasks, in case the CR, that has child tasks, is imported. | No. | Yes. |
18 | Importing planned dates. | Yes. Imports only duration. | Yes. Imports planned start and finish dates. |
19 | Importing owners for a task. | Yes. | Yes. |
20 | Dynamic importing of users into the plan. | Yes. | Yes. |
21 | Importing dependencies between tasks. | No. | Yes. |
22 | Automatic transition of a task into the next state, if an owner is assigned. | No. | Yes. |
Saving the plan into ClearQuest |
23 | Saving tasks. | Yes. | Yes. |
24 | Saving selected tasks only. | Yes. | Yes. |
25 | Saving planned dates. | Yes. | Yes. |
26 | Saving owners for tasks. | Yes. | Yes. |
27 | Saving additional fields. | Yes. | Yes. |
28 | Creating new ClearQuest requests on a basis of the plan. | Yes. | Yes. |
29 | Automatic creation of hierarchical relations between CRs on a basis of hierarchical relations between tasks in the plan. | No. | Yes. |
30 | Automatic creation of dependencies between CRs on a basis of dependencies between tasks in the plan. | No. | Yes. |
Updating the MS Project plan from ClearQuest |
31 | Updating information on tasks. | Yes. | Yes. |
32 | Updating planned dates. | Yes. The package does not allow modifying planned dates from ClearQuest. | Yes. Optional. |
33 | Updating owners for a task. | Yes. | Yes. Optional. |
34 | Updating values in additional fields. | Yes. | Yes. |
35 | Updating actual dates. | Yes. | Yes. |
36 | Updating actual work effort. | Yes. | Yes. |
Integration with IBM Rational ClearQuest ALM |
37 | Supporting integration using one type of CR. | Yes. | Yes. |
38 | Supporting several types of CRs without creating hierarchical relations on the MS Project plan. | Yes. | Yes. |
39 | Supporting several types of CRs using hierarchical relations on the MS Project plan. | No. | Yes. Full support of all hierarchical relations that are provided by this scheme type. |
Additional features |
40 | Opening ClearQuest forms of CRs for tasks from the MS Project plan. | No. | Yes. |
41 | Changing states of the CR from the MS Project plan. | No. | Yes. |
42 | Creating new ClearQuest CRs that are not related to the MS Project plan from MS Project. | No. | Any CR types. |
Articles and Media 
