Skip to main content
Planview Customer Success Center

IBM Rational ClearQuest

IBM Logo




Large scale software development requires adherence to process but with the flexibility to orchestrate complex, custom workflows.



Connector Setup Details

This section describes the basic steps needed to prepare your IBM Rational ClearQuest instance for use with Viz. 

Minimal User Permissions & Viz User

We recommend that you create a new user within your external tool, to be used only for Viz. This is the user information you will enter when setting up your tool connection within Planview Viz. By creating a new user, you will ensure that the correct permissions are granted.

In general, your user account should have sufficient permissions to read artifacts in your tool. 

Your user should have a secure password or token. Please be aware that Viz will not allow you to save a tool connection utilizing a weak password/token, such as 'tasktop.'

See instructions on how to create a custom user in IBM Rational ClearQuest.

Connecting to the IBM Rational ClearQuest Repository

Standard Authentication

Required Fields:

ClearQuest Repository Name

Optional Fields:

  • Test Database Names:
    • A comma separated list of test database names. This can be found in ClearQuest Designer in Database Admin for your Tool.

Test Database Names

IBM Rational ClearQuest Tool Connection Screen



Supported Artifacts

Supported Work Items

Supported Work Item Type

Applicable Repository Version

Unique URL?

All resources that are stateful and submittable. By enabling default templates, you will have artifacts like:

  • ALM Task
  • ALM Request
  • ALM Defect

Any supported repository version:


Supported Containers

Containers that can be modeled as Flow Items

Applicable Repository Versions

Unique URL?




Containers used to define which artifacts are included in an Artifact Set




Any supported repository version:




Supported Field Types

Planview Viz supports configuring rule-based modeling (i.e., conditional modeling) using the field types shown below.

Note: If one field of a given type is supported, others that are also that type in theory should also work. However, sometimes there are instances in which this is not the case due to the repository. So, while we can claim support for fields at the type level, there is a chance that some specific fields of a given type will not function properly.


Standard Field Type

How is field type referenced in the repository?

Sample Repository Fields Supported

Particular Repository Fields NOT Supported

1checkicon.png String

Short String

Multi Line String

Formatted ID




1checkicon.png Single Select

Short String/Reference - Constant List

Short String/Reference - Perl





1checkicon.png Multi Select

Reference List


Category Path


1Not_allowed.svg.png Boolean