|
'ProjectTracker for MSP Server 2003 & 2007' MS Project and MSP Server and ClearQuest integration module. This tool is registered as the V.A.P-solution in IBM. State-of-art MS Project (Project Server 2003 & 2007) and ClearQuest integration module which allows bidirectional collaboration keeping the full hierarchy, total resources information and all dependencies as well. During planning in MS Project the module allows to import all resources available from the CQ base. It’s irreplaceable tool for excellent project management.
Contents
1. List of abbreviations, conventions and terms 2. Glossary 3. Introduction 3.1 Purpose of This Document 3.2 Field of Application 3.3 Implementation 3.4 System Requirements 4. General Description 4.1 Usage variants 5. Functionality 6. Description of User Interface Forms 6.1 Authorization 6.2 Configuration 6.3 Saving 6.4 Importing 6.5 Refreshing 7. Adjusting Module Settings 7.1 Main record settings 7.2 Project record settings 7.3 Additional record setting 7.4 Additional fields settings 7.5 Resource settings 7.6 Additional settings 8. Using the Program 8.1 Saving Tasks 8.2 Creating a Query for Import in ClearQuest 8.3 Importing 8.4 Refreshing 8.5 Opening a User Interface Form of the ClearQuest Request from MS Project 8.6 Creating a New ClearQuest Request 8.7 Importing a License Key 1.List of abbreviations, conventions and terms | Abbreviation | Expansion | | ProjectTracker | MS Project and ClearQuest Integration Module | | MS | Microsoft | | MPS, MS Project | Microsoft Office Project Professional 2003/2007 | |
|
|
2.Glossary | Term | Interpretation | | ClearQuest | Software change management system IMB Rational ClearQuest | | ClearQuest entity type | ClearQuest entity (Defect, Task, etc.) |
3.Introduction 3.1Purpose of This Document The document provides users with information on functionality of the ProjectTracker module which allows effectively using MS Project and ClearQuest as a single integrated system. The document covers the following topics: 3.2Field of Application The document relates to the ProjectTracker module, and is intended for the end user (project manager) of the change management system.
3.3Implementation The module is implemented as an add-on for MS Project, and is integrated into the MS Project menu. The module represents a COM object implemented in the .NET 2.0 framework.
3.4System Requirements
4.General Description The module is intended for integration of ClearQuest and MS Project, and allows performing tighter integration than the standard IBM Rational module can provide. When performing integration of the ClearQuest base and the MS Project plan, the module allows mapping entity properties (synchronized data) using flexible settings. The module supports hierarchical relations between ClearQuest requests thus it allows keeping several child (nesting) tasks and subtasks in the plan, which will be synchronized with tasks of the MS Project plan. The module allows a manager to plan work of their employees using MS Project directly. By means of integration, you can open the Clear Quest record forms, and synchronize any fields, displaying them directly in the MS Project plan. The main feature of this module that distinguishes it from the standard one is the possibility to automatically form dependency links between ClearQuest requests. This possibility allows a manager to plan work in more detail directly in MS Project, which is more handy and usual for them. The module performs synchronization of information between the ClearQuest and MS Project systems using the following basic data exchange operations (see Figure 1 – Basic operations):
 Figure 1 – Basic operations
4.1Usage variants This section contains information on variants of using hierarchical relations for integration, and using the fields of ClearQuest requests. For the list of necessary fields, and details on their use, see the Configuration section.
Project-Request-Task Hierarchy
The Project Tracker module supports various request hierarchies, defined in the task plan, or the ClearQuest database. The figure below (see Figure 2 – Project-Request-Task relationship) describes the Project-Request-Task relationship between ClearQuest entities and Ms Project tasks.  Figure 2 – Project-Request-Task relationship
Desription of the Project-Request-Task relationship: In this hierarchy type, the following types of ClearQuest entities are used, and they are associated with the following tasks of the MS Project plan: The Project type of ClearQuest entity – the first nesting level The Request type of ClearQuest entity – the second nesting level The Task type of ClearQuest entity - the thirds and subsequent nesting levels
The ClearQuest entity type used for identification of a project must comply with the following requirements: Availability of the following fields: Name – mandatory Description – optional Owner - optional Percent complete – optional Plan start date – optional Plan finish date – optional Actual start date – optional Actual finish date – optional Planned cost – optional Actual cost – optional Task reference – optional Request reference – optional
An action available that provides a possibility to edit a record
The ClearQuest entity type used for identification of additional requests (defect, task, etc.) must comply with the following requirements: Availability of the following fields: Headline – mandatory Description – optional Plan start date – optional Plan finish date – optional Child task reference - optional, in case tasks have references to requests Project reference – mandatory, in case project does not have references to requests
An action available that provides a possibility to edit a record
The ClearQuest entity type used for identification of a task must comply with the following requirements: Availability of the following fields: Headline – mandatory Description – optional Plan start date – mandatory Plan finish date – mandatory Actual start date – mandatory Actual finish date – mandatory Owner – mandatory Child task reference – mandatory, in case implementation of task hierarchy is necessary Parent task reference – mandatory, in case implementation of task hierarchy is necessary Project reference – mandatory, in case there is no reference to tasks from the project Request reference – mandatory, in case there is no reference from the request to tasks Predecessors – optional Plan work – optional Actual work – optional
An action available that provides a possibility to edit a record
Project-Task Hierarchy
The figure below (see Figure 3 – Project-Task relationship) describes the Project-Task relationship between ClearQuest entities and MS Project tasks.  Figure 3 – Project-Task relationship
Description of the Project-Task relationship: In this hierarchy type, the following types of ClearQuest entities are used, and they are associated with the following tasks of the MS Project plan: The Project type of ClearQuest entity – the first nesting level The Task type of ClearQuest entity - the second and subsequent nesting levels
The ClearQuest entity type used for identification of the project must comply with the following requirements: Availability of the following fields: Name – mandatory Description – optional Owner - optional Percent complete – optional Plan start date – optional Plan finish date – optional Actual start date – optional Actual finish date – optional Planned cost – optional Actual cost – optional Task reference – optional
An action available that provides a possibility to edit a record
The ClearQuest entity type used for identification of a task must comply with the following requirements: Availability of the following fields: Headline – mandatory Description – optional Plan start date – mandatory Plan finish date – mandatory Actual start date – mandatory Actual finish date – mandatory Owner – mandatory Child task reference – mandatory, in case implementation of task hierarchy is necessary Parent task reference – mandatory, in case implementation of task hierarchy is necessary Project reference – mandatory, in case there is no reference to tasks from the project Predecessors – optional Plan work – optional Actual work – optional
An action available that provides a possibility to edit a record
Request-Task Hierarchy
The figure below (see Figure 4 – Request-Task relationship) describes the Request-Task relationship between ClearQuest entities and MS Project tasks.  Figure 4 – Request-Task relationship
Description of the Request-Task relationship: In this hierarchy type, the following types of ClearQuest entities are used, and they are associated with the following tasks of the MS Project plan: The Request type of ClearQuest entity – the firts nesting level The Task type of ClearQuest entity – the second and subsequent nesting levels
The ClearQuest entity type used for identification of additional requests (Defect, Enhancement, Request etc.) must comply with the following requirements: Availability of the following fields: Headline – mandatory Description – optional Plan start date – optional Plan finish date – optional Child task reference - optional, in case tasks have references to requests
An action available that provides a possibility to edit a record
The ClearQuest entity type used for identification of a task must comply with the following requirements: Availability of the following fields: Headline – mandatory Description – optional Plan start date – mandatory Plan finish date – mandatory Actual start date – mandatory Actual finish date – mandatory Owner – mandatory Child task reference – mandatory, in case implementation of task nesting is necessary Parent task reference – mandatory, in case implementation of task nesting is necessary Request reference – mandatory, in case there is no reference from the request to tasks Predecessors – optional Plan work – optional Actual work – optional
An action available that provides a possibility to edit a record
Task-Task Hierarchy
The figure below (see Figure 5 – Task-Task relationship) describes the Task-Task relationaship between ClearQuest entities and MS Project tasks.
 Figure 5 – Task-Task relationship
Description of the Task-Task relationship: In this hierarchy type, the following types of ClearQuest entities are used, and they are associated with the following tasks of the MS Project plan: The Task type of ClearQuest entity - the firtst and subsequent nesting levels
The ClearQuest entity type used for identification of a task must comply with the following requirements: Availability of the following fields: Headline – mandatory Description – optional Plan start date – mandatory Plan finish date – mandatory Actual start date – mandatory Actual finish date – mandatory Owner – mandatory Child task reference – mandatory Parent task reference – mandatory Predecessors – optional Plan work – optional Actual work – optional
An action available that provides a possibility to edit a record
5.Functionality The ProjectTracker module supports the following functionality: Supports hierarchical relations in ClearQuest requests Allows importing requests from the ClearQuest database into MS Project plan with restoration of ClearQuest request hierarchy (the module supports hierarchical relations not only between requests of the same type, but also between requests of different types) Supports synchronization of any types of fields Imports user accounts from the ClearQuest database, and allows using them as resources in the MS Project plan Uses special settings, regulating synchronization priorities Does not require installing special packages on records in the ClearQuest scheme Integrates into MS Project completely, and allows opening ClearQuest request forms from the shortcut menu
6.Description of User Interface Forms After the installation, the ProjectTracker integrates with MS Project by adding a menu, and building in the separate toolbar (see Figure 6 – Integrated menu).  Figure 6 – Integrated menu
The menu and the toolbar provide access to the following functions:  Connect – connecting to ClearQuest;
 New – creating a new ClearQuest request
 Open CQ Form – opening a form of the selected ClearQuest request;
 Import to MSP – importing ClearQuest requests into the MS Project plan;
 Import child records – importing child requests for the selected ClearQuest request;
 Save Plan to CQ – saving a whole plan to ClearQuest;
 Save Selection to CQ – saving the requests selected from the plan to ClearQuest;
 Refresh MSP Plan – refreshing a whole MS Project plan from ClearQuest;
 Refresh MSP Selection – refreshing the selected MS Project plan requests from ClearQuest;
Settings – opening a form for adjusting the module settings; About – opening a window with the module description.
6.1Authorization The authorization dialog (see Figure 7 – ClearQuest session authorization window) is the standard authorization window that appears when the ClearQuest database session is initiated.  Figure 7 – ClearQuest session authorization window
6.2Configuration In the Configuration dialog, there are six tabs: The Main tab – allows adjusting the main request fields necessary for planning The Project tab – allows configuring mapping between the ClearQuest request and the project, fields of the MS Project plan The Add request tab – allows configuring the ClearQuest additional requests that should be reflected in the plan The Add fields tab – if necessary, the tab allows configuring the ClearQuest request’s additional fields that will be included into the plan The Resources tab – allows configuring automatic import of ClearQuest or MS Project Server users into the plan The Add settings tab – allows adjusting the following parameters: default request, switching off automatic calculation, etc.
The Main Tab
The main request is the ClearQuest request that is used as a task to an end owner, and is associated with a task in the MS Project plan. In the Main tab, (see Figure 8 – The Main tab) you can adjust settings of the ClearQuest main request. The tab contains the following properties: Record type – the ClearQuest request type intended for associating tasks of the MS Project plan with it Edit – a name of the action that will be used for editing records in ClearQuest Assignee action – a name of the action that should be taken to assign an owner for a task Change only plan dates and resources – if this option is selected, only plan dates and resources will be saved in ClearQuest upon refreshing. Otherwise, all changed fields of the task will be saved. Update plan dates and resources from CQ – select this option, if plan dates and resources edited in ClearQuest should be updated in the MS Project plan as well upon the MS Project plan refreshing Otherwise, these changes will be ignored and rewritten upon saving the plan in ClearQuest. Headline – this field contains a brief description of the ClearQuest request, and will be converted into the Name field of a task in the plan Description – this field contains a detailed description of the ClearQuest request, and will be converted into the Note field of a task in the plan Resources – this field contains a name of an owner in the ClearQuest request Plan start date – this field contains a planned date for starting work in the ClearQuest request Plan finish date – this field contains a planned date for finishing work in the ClearQuest request Plan assignment work – this field contains planned effort of an owner in ClearQuest. The value can be set in percentage, or in hours. If you set the value in percentage, it will represent a planned owner’s load in percentage relative to a whole task duration. Actual start date – this field contains an actual work start date in the ClearQuest request Actual finish date – this field contains an actual work finish date in the ClearQuest request Actual assignment work – this field contains a value of time spent on a task The value can be set in percent, or in hours. Child record reference – the field that represents a reference to a child request. The field must refer to the same request type, that is defined in the Record type configuration field. Parent record reference – the field that represents a reference to a parent request. The field must refer to the same request type, that is defined in the Record type configuration field. Predecessors – this filed contains references to the ClearQuest request (the references that must precede this request). The field must refer to the same request type, that is defined in the Record type configuration field, and is responsible for displaying the sequence in MS Project.
 Figure 8 – The Main tab
The Project Tab
On this tab, you can configure the ClearQuest request that corresponds to the project. The project in the MS Project plan, if it is configured, can be associated with the first level task only. The number of projects in a plan is not limited. This tab contains the following fields: Record type – the ClearQuest request type that represents a project in the ClearQuest system Edit action – Edit – the action that should be performed to edit a project record in the ClearQuest system. This action should be defined if it is necessary to synchronize planned and actual dates, completion rate, project costs in the MS Project plan with those in the ClearQuest system, and if it is necessary to link child requests directly from the project entity in ClearQuest. Use baseline for planning – select this option, only if it is necessary to edit planned dates of the ClearQuest project from MS Project. In this case, the baseline defined in additional settings will be used. Headline – the ClearQuest request field that corresponds to the project name Description – the ClearQuest request field that contains additional information on the project Project manager – the ClearQuest request field that contains a project manager resource Plan start – the ClearQuest request field that contains a planned date of starting a project. You should fill in this field, if the planned date of starting a project will be set from MS Project. Plan finish – the ClearQuest request field that contains a planned date of finishing a project. You should fill in this field, if the planned date of finishing a project will be set from MS Project. Plan cost – the ClearQuest request field that contains a planned project costs Actual start – the ClearQuest request field that contains an actual date of starting a project. You should fill in this field, if the actual date of starting a project will be set from MS Project. Actual finish – the ClearQuest request field that contains an actual date of finishing a project. You should fill in this field, if the actual date of finishing a project will be set from MS Project. Actual cost – the ClearQuest request field that contains actual project costs Task reference – the ClearQuest request field that contains a list of all project tasks Project reference from main record – the field of the ClearQuest main request that contains a name of a project corresponding to the main request Percent – the ClearQuest request field that contains an actual project completion rate. If the rate is set, then in the ClearQuest request, there will be set a completion rate of the task that is associated with this request. State – the ClearQuest request field that defines a project state, if a project is defined using a reference
 Figure 9 – The Project tab
The Add Record Types Tab
Additional requests are requests that initiate a task definition (defect, request from an interested party, etc.) The distinctive feature of these requests is that you cannot edit any of their fields in ClearQuest from MS Project. You can only bind child tasks to such requests. To configure the ClearQuest additional requests, use the Add record types tab. This tab (see Figure 10 – The Add record types tab) contains the following fields: Record type – configurable ClearQuest request type Edit – a name of the action that will be used for generating child requests in ClearQuest; Headline – this field contains a brief description of the ClearQuest request Description – this field contains a detailed description of the ClearQuest request Resource – this field contains a name of an owner in the ClearQuest request Plan start date – this field contains a plan date for starting work in the ClearQuest record; Planned finish date – this field contains a plan date for finishing work in the ClearQuest record; Child record reference – the field that represents a reference to a child request. The field must refer to the same request type, that is defined in the Record type configuration field on the Main tab Reference from main record – this field contains a reference from the main request to an additional request Project reference – the ClearQuest request field that contains a project name Reference from project – the ClearQuest request field that refers to a configurable additional request List with results – this table contains all configured additional requests Add – click this button to add new requests to a table Delete – click this button to delete any of the configured additional requests from a table Change – click this button to adjust settings of a record selected from the table of additional requests
 Figure 10 – The Add record types tab
The Add Fields Tab
Additional fields are the ClearQuest request fields that should be displayed in the MS Project plan. Besides, you must have an ability to edit these fields from MS Project. You can configure the ClearQuest request additional fields on the Add fields tab that is described below. This tab (see Figure 11 – The Add fields tab) contains the following fields: Custom CQ Entity – the entity for which an additional field is configured Name ClearQuest field – the configurable ClearQuest field that should be displayed in a plan; Visible name – a field name that will be displayed in the plan title MSProject field – an identifier of the MS Project field, into which the value from the ClearQuest field will be copied Is visible – if you select this option, a configurable field will be added to the plan as visible. Otherwise, this field will not be displayed in the plan, though values will be recorder to the field. Access – defines a method of using a configured field Read/Write – a value in a field will be updated from the ClearQuest record every time the plan is refreshed from ClearQuest, and a field value from the MS Project plan will be recorded into the ClearQuest record every time the plan is saved in ClearQuest Read – a field value will only be updated from the ClearQuest request every time the plan is refreshed from ClearQuest; Write – a field value will only be recorded from the MS Project plan into the ClearQuest request every time the plan is saved in ClearQuest
List – if you select this option, a configurable field will represent a list Reference to – this option allows defining that a field represents a reference to another ClearQuest entity. There are four fields under this option: record type – contains a list of ClearQuest entities From this list, select the ClearQuest entity that is referenced by this field. field – contains a list of fields that are above the selected entity From this list, select a field name that will be displayed in the MS Project plan filter – a list of fields by which you can filter a list value – an filtering expression
Named list – defines a dynamic list that can be associated with a field List with results – this table contains all configured additional fields Add – click this button to add a new field Delete – click this button to delete any of the configured fields from a table Change – click this button to adjust settings of a field selected from a table
 Figure 11 – The Add fields tab
The Resources Tab
On the Resources tab (see Figure 12 – The Resources Tab), you can adjust settings for owners: Autoload users to MSProject plan – if you select this option, the integration module will automatically generate a list of resources If none of the options listed below is selected, all users defined in the User entity of the ClearQuest will be downloaded. Use non-standard user entity – if you select this option, a non-standard User entity will be used Record type – a name of the User entity Resource – the entity field containing an owner ’s name Description – a detailed description of a user Email – the field containing a user’s e-mail Phone – the field containing a users’ phone number
Use db access for MSProject Server – if you select this option, a list of users will be downloaded from the MS Project server when importing or refreshing tasks Database server – a name of a database server that hosts the MS Project Server databases Database name – a name of the MS Project Server database User name – a name of a user who have a read access to the MS Project Server database Password – a password of a user defined above
Use plan assignment in – in this list, you can select a unit of measure for planned work load (percentage or hours) Use actual work in – in this list, you can select a unit of measure for actual work completion (percentage or hours)
 Figure 12 – The Resources Tab
The Add Settings Tab
On this tab (see Figure 13 – The Add settings tab), you can configure additional setings: Default query – this field contains a path to a filter query that will be used for importing the ClearQuest records The entered path will be saved for a project that is opened during configuration of integration module. Every task have ClearQuest record – if you select this option, the Clear Quest record field will not be used for identification of ClearQuest records Autocalculate off – if you select this option, then automatic calculation during import, refresh and save operations is switched off, that allows speeding up these operations ClearQuest Record – the system field that is used for identification of the ClearQuest records CQID – the system field that contains the identifier of the ClearQuest record Record Type – the system field that contains a name of the ClearQuest record type State – the system field that contains a value of the State field of the ClearQuest record Use baseline for planning – if you select this option, then the set planned dates will be duplicated into the baseline selected below Baseline – in this list, you can select a baseline that will store the planned dates Use default CQ values – if you select this option, default values will be saved during the save operation The entered path will be saved for a project that is opened during configuration of integration module. Field – a name of the ClearQuest main record field that will store default values Value – a default value A default value can be static, or can be equal to the value of any MS Project field. In the latter case, the field name should be set in square brackets. Update: always – a value will be recorded into the ClearQuest record field upon every saving of the plan in ClearQuest empty – a value will be recorded into the ClearQuest record field upon saving of the plan in ClearQuest only if the field is empty
List with results – this table contains all configured default values Add – click this button to add new value to a table Delete – click this button to delete any of the configured records from a table
 Figure 13 – The Add settings tab
6.3Saving After you have selected the Save Plan to CQ or Save Selection to CQ option from the menu, the Save dialog opens (see Figure 14 – Launching the Export dialog). The dialog contains the folowing elements: The text box with a log of save operation The Start button to launch saving The Stop button to stop saving The Close button to close the Save dialog The Change state if task assigned option – if a resource is assigned for a task, the ClearQuest request is converted into a next state by the Assignee action
 Figure 14 – Launching the Export dialog
Export log is displayed in the following format (see Figure 15 – Export log):  Figure 15 – Export log
6.4Importing The Import dialog opens when you select the Import to MSP or Import child records option from the menu (see Figure 16 – Launching the Import dialog). The dialog contains the following elements: The text box with a log of import operation The Start button to launch importing The Stop button to stop importing The Close button to close the Import dialog The Use default query option– if this option is selected, the import operation will be performed using the query defined in the Default query field on the Add settings tab
 Figure 16 – Launching the Import dialog
If you click Start with the Use default query option not selected, the ClearQuest filter form will open (see Figure 17 – Selecting requests for importing), otherwise the form will not open. To procced with imporing, you should select filtered records, and click OK.
 Figure 17 – Selecting requests for importing
Import log is displayed in the following format (see Figure 18 – Import log):  Figure 18 – Import log 6.5Refreshing The Refresh dialog opens when you select the Refresh MSP plan or Refresh MSP selection option from the menu (see Figure 19 – Launching the Synchronization dialog). The dialog contains the following elements: The text box with a log of refresh operation The Start button to launch refreshing The Stop button to stop refreshing The Close button to close the Refresh dialog
 Figure 19 – Launching the Synchronization dialog
The refresh log is displayed in the following format (see Figure 20 – Synchronization log):
 Figure 20 – Synchronization log
7.Adjusting Module Settings To open the form for adjusting the module settings, select Settings from the module menu (see Figure 21 – Adjusting module settings).
 Figure 21 – Adjusting module settings
To configure the module, you should fill in all the fields listed below. To save the adjusted module settings, click Save. To cancel changes, click Cancel.
7.1Main record settings You should configure the main fields for every request type that should be included into a plan. The properties of the main fields are described in the Configuration section. To configure the main fields, follow the steps below: From the Record Type list, select the ClearQuest request type that corresponds to the main request From the Edit field, select a name of an action that will be used for editing the ClearQuest records From the Assignee action, select a name of an action that will be used for converting the ClearQuest request into the next state upon assigning a resource for a task Select the Change only plan dates and resources option, if only planned dates and resources should be changed upon saving values into the available ClearQuest request Select the Update plan dates and resources from CQ option, if changes of planned dates and resources made in ClearQuest should be applied to corresponding tasks of the MS Project plan upon refresh operation From the Headline list, select a name of a field that corresponds to the main ClearQuest request From the Description list, select a name of a field that contains a detailed description of the main ClearQuest request From the Headline list, select a name of a field that corresponds to the main ClearQuest request From the Plan start date list, select a name of a field corresponding to a planned date of starting work in the main ClearQuest request From the Plan finish date list, select a name of a field corresponding to a planned date of finishing work in the main ClearQuest request From the Plan assignment work list, select a name of a field corresponding to a planned work load in the main ClearQuest request From the Actual start date list, select a name of a field corresponding to an actual date of starting work in the main ClearQuest request From the Actual finish date list, select a name of a field corresponding to an actual date of finishing work in the main ClearQuest request From the Actual assignment work list, select a name of a field corresponding to an actual rate of work completion in the main ClearQuest request From the Child record reference list, select a name of a field that represents a reference to a child main ClearQuest request From the Parent record reference list, select a name of a field that represents a reference to the parent main ClearQuest request From the Predecessors list, select a name of a field that represents a reference to the preceding main ClearQuest request
7.2Project record settings To configure project request, follow the steps below: From the Record Type list, select a name of a request type From the Edit field, select a name of an action that will be used for generating child records From the Headline list, select a name of a field that corresponds to the project ClearQuest request From the Description list, select a name of a field that contains a detailed description of the project ClearQuest request From the Project managerlist, select a name of a field that corresponds to a project manager of the project ClearQuest request From the Plan start list, select a name of a field corresponding to a planned date of starting work in the project ClearQuest request From the Plan finish list, select a name of a field corresponding to a planned date of finishing work in the project ClearQuest request From the Plan cost list, select a name of a field corresponding to a planned costs of works in the project ClearQuest request From the Actual start list, select a name of a field corresponding to an actual date of starting work in the project ClearQuest request From the Actual finish list, select a name of a field corresponding to an actual date of finishing work in the project ClearQuest request From the Actual cost list, select a name of a field corresponding to an actual costs of works in the project ClearQuest request From the Task reference list, select a name of a field that represents a reference to the main ClearQuest request From the Project reference from main record list, select a name of a field that represents a reference from the main ClearQuest request to the project ClearQuest request From the Percent list, select a name of a field corresponding to a work completion rate in the project ClearQuest request From the Statelist, select a name of a field corresponding to a work completion rate in the project ClearQuest request
7.3Additional record setting Settings of additional requests can be of two types: main settings and relationship settings. The main settings include a general description of the additional request, and relations of the additional request to the main request, and a project. Relationship settings define relations between additional requests. To configure the main settings, follow the steps below: From the Record Type list, select a name of a record type From the Edit field, select a name of an action that will be used for binding child requests From the Headline list, select a name of a field that corresponds to the additional ClearQuest request From the Description list, select a name of a field that contains a detailed description of the additional ClearQuest request From the Resourcelist, select a name of a field that corresponds to an owner of the additional ClearQuest request From the Planned start date list, select a name of a field corresponding to a planned date of starting work in the additional ClearQuest request From the Planned finish date list, select a name of a field corresponding to a planned date of starting work in the additional ClearQuest request From the Child record reference list, select a name of a field that represents a reference to a main ClearQuest request From the Reference to main record list, select a name of a field that represents a reference from the main ClearQuest request to the additional ClearQuest request From the Project reference list, select a name of a field that represents a reference to the project ClearQuest request From the Reference from project list, select a name of a field that represents a reference from the project ClearQuest request to the additional ClearQuest request Click Add
To configure relations between additional requests, follow the steps below: From the Record Type list, select the ClearQuest request type with the main settings configured From the Reference entity name list, select the name of the field From the Reference field name list, select the name of the field From the BackReference field name list, select the name of the field From the Hard reference list, select the necessary relationship type Click Add
To edit values in the table with results, follow the steps below: In the table, select a line that to be edited Change corresponding values Click Edit
To delete lines from the table with results, follow the steps below: In the table, select a line that to be deleted Click Delete
7.4Additional fields settings To configure the additional fileds, you should add lines to the Add fields table. The properties of the main fields are described in the Configuration section.
To configure the additional settings, follow the steps below: From the Custom CQ Entity list, select a name of the ClearQuest request type From the Name ClearQuest field list, select the name of the ClearQuest request field From the MSProject field list, select a name of the MS Project field Select the necessary type of access to a field If the field represents a list in the ClearQuest record, select the List option If the field represents a reference to the record, select the Reference option From the Record type list, select a type of the record that is referenced by the field From the Field list, select the field of the record type defined above (the value in this field is used for the reference) To create a filter, select the necessary Filter field that will be used for filtering, and click +. In the Value field, type the value of the filter after the = sign.
If the field represents a dynamic list, select the Named List field, and the list name from the field that is being activated
Click Add
To edit values in the table with results, follow the steps below: In the table, select a line that to be edited Change corresponding values Click Change
To delete lines from the table with results, follow the steps below: In the table, select a line that to be deleted Click Delete
7.5Resource settings To configure the resource settings, follow the steps below: If users should be downloaded automatically into the plan, select the Autoload users to MSProject plan option If identification of owners should be performed using the ClearQuest entity different from the Users entity, select the Use non-standard user entity option From the Record Type list, select the necessary entity Select the Resource field that contains an owner’s name Select the Description field that contains a detailed description of an owner Select the Email field that contains an owner’s e-mail Select the Phone field that contains an owner’s phone number
If users should be downloaded from the global pool in MS Project Server, select the Use db access for MSProject Server option In the Database server field, define a name of server hosting MS Project Server databases In the Database name field, define a name of the MS Project Server database In the User name field, define a user name for accessing the database server hosting MS Project Server In the Password field, define a password of the user defined above
From the Use plan assignment in list, select variants of planned workload change From the Use actual work in list, select variants of actual workload change
7.6Additional settings To configure additional settings, follow the steps below: Request is configured by default for every new project of MS Project Click Select, and from the opened window, select a record type for which a request should be selected (see Figure 22 – Choosing a record type for the request), then click OK
 Figure 22 – Choosing a record type for the request
In the opened window, select the necessary request, and click Run or double-click the request to run it (see Figure 23 – Selecting a request); then click OK
 Figure 23 – Selecting a request
To remove association between the project and the request, click Clear
If the Every task have ClearQuest record option is selected, the ClearQuest field in the plan will be ignored, and all tasks in the plan will be processed upon save, import and refresh operations If the Autocalculate off option is selected, automatic calculation will be switched off before all operations that significantly increase the module performance when there is a large number of tasks After the operations are completed, the project is recalculated, and automatic calculation switches on Special fields – all system fields necessary for the plan should be filed in System fields should be used only for synchronization, and should not be changed needlessly If some fields should not be displayed in the plan, they can be hidden Using default values: From the Field list, select a name of the ClearQuest field In the Value field, enter the default value Select the necessary method of using the field – always or empty Click Add To delete the unnecessary field, click Delete
8.Using the Program 8.1Saving Tasks For expoting the exisiting task plan from MS Project into ClearQuest, it is necessary that the list of tasks have already been generated in MS Project, and properties necessary for ClearQuest have been already set. The section below provides details on exorting the task plan: Connect to the ClearQuest database (see Figure 24 – Connecting to the ClearQuest database)
 Figure 24 – Connecting to the ClearQuest database
After the connection is established successfully, the additional columns will be added (see Figure 25 – Additional columns).  Figure 25 – Additional columns
Add new tasks, all necessary fields, and set a value of the ClearQuest field in CQEntity
 Figure 26 – New tasks for saving
Save the list of tasks (see Figure 27 – Saving tasks)
 Figure 27 – Saving tasks If the operation completes successfully, the following log will open (see Figure 28 – Export log)  Figure 28 – Export log
After exporting, in the MS Project plan, system fields will be assigned to tasks (see Figure 29 – Result of exporting tasks)
 Figure 29 – Result of exporting tasks
After saving, in ClearQuest, new tasks will appear (see Figure 30 – New records in ClearQuest)
 Figure 30 – New records in ClearQuest
If the Predecessors field is configured in the module settings, then the preceding records corresponding to tasks in the MS Project plan will be automatically added into this field (see Figure 31 – Predecessor records in ClearQuest)
 Figure 31 – Predecessor records in ClearQuest
If the Child record reference field is configured in the module settings, then the child records corresponding to tasks in the MS Project plan will be automatically added into this field (see Figure 32 – Child records in ClearQuest)
 Figure 32 – Child records in ClearQuest
8.2Creating a Query for Import in ClearQuest The section below describes the steps you need to follow to create a query: start ClearQuest and open the corresponding workspace to create a new query, right-click the folder where the query will be stored, and click New Query
 Figure 33 – Creating a new query
In the Choose Record Type window, select a record type that should be synchronized with the MS Project plan, and click OK
 Figure 34 – Record type for query
Enter the query name, and click Enter
 Figure 35 – Query name
To launch the ClearQuest query wizard, double-click the name of the new query, and then click Next
 Figure 36 – Query wizard – step 1
Select the list of fields displayed in the query resulting report , anmd click Next
 Figure 37 – Query wizard – step 2
Select a filtering type, if necessary
 Figure 38 – Query wizard – step 3
After the filter is configured, click Run. The query will be executed, and its result will be displayed (see Figure 39 – Query result)
 Figure 39 – Query result Save the query using the Save command in the File menu
8.3Importing To import tasks from ClearQuest, follow the steps below: Connect to ClearQuest (see Figure 40 – Selecting an operation of importing tasks) From the menu of the integration module, select the Import to MSP option (see Figure 40 – Selecting an operation of importing tasks)
 Figure 40 – Selecting an operation of importing tasks
If you want to use the query configured by default, the in the opened window (see Figure 41 – Launching the Import dialog), select the Use default query option, and click Start
 Figure 41 – Launching the Import dialog
If you have not selected the Use default query option, then the window will open, where you should select a query, run it, and, from the query results, select records that should be imported into the MS Project plan (see Figure 42 – Selecting tasks for importing )
 Figure 42 – Selecting tasks for importing
In the Import window, in the log field, the list of imported tasks will be displayed (see Figure 43 –Import log)
 Figure 43 –Import log
In the plan, the imported tasks will be displayed (see Figure 44 –Result of importing tasks)
 Figure 44 –Result of importing tasks 8.4Refreshing The synchronization mode is necessary for refreshing tasks in the plan. To refresh tasks, perform the following steps: Open the up-to-date MS Project plan, and establish connection with ClearQuest From the menu of the integration module, select the Refresh MSP plan option (see Figure 45 – Selecting a synchronization operation)
 Figure 45 – Selecting a synchronization operation
In the opened window (see Figure 46 – Launching the Synchronization dialog), click Start
 Figure 46 – Launching the Synchronization dialog
The Synchronization log window will open (see Figure 47 –Synchronization log)
 Figure 47 –Synchronization log
8.5Opening a User Interface Form of the ClearQuest Request from MS Project From MS Project, you can open the ClearQuest request form. To open the form, in the plan, select a task that is associated with the ClearQuest request (for this record, the ClearQuest identifier is defined); then, from the menu of the integration module, select Open CQ form (see Figure 48 – Opening a ClearQuest request form). The ClearQuest form of the selected request will open (see Figure 49 – ClearQuest request opened from MS Project).  Figure 48 – Opening a ClearQuest request form
 Figure 49 – ClearQuest request opened from MS Project
8.6Creating a New ClearQuest Request
The integration module supports creation of new ClearQuest request from MS Project. To create a new request, follow the steps below: From the menu of the integration module, select New
 Figure 50 – Creating a new ClearQuest request
The dialog window with the list of all ClearQuest requests will open. Select the necessary ClearQuest request, and click OK
 Figure 51 – Selecting a type of the ClearQuest request
In the form of the new ClearQuest request, fill in all the fields, and click OK
 Figure 52 – Form of a new ClearQuest request 8.7Importing a License Key
Without a license key, the module works in demonstration mode (see Figure 53 – Demonstration mode). In the demonstration mode, only the following functions are available: Importing ClearQuest requests into the MS Project plan Creating a new ClearQuest request Accessing forms of ClearQuest requests that were imported into the MS Project plan
 Figure 53 – Demonstration mode
To import a license key, follow the steps below: From the menu of the integration module, select About
 Figure 54 – Importing a license key
In the opened window, click Import license
 Figure 55 – About window
select the location of the license key on the local disk
 Figure 56 – Selecting a license key
After the license key is imported, restart MS Project to activate the key
 Figure 57 – Successful import of the license key
Tags:
Add more tags...,
|
Articles and Media 
