Skip to main content
Planview Customer Success Center Release Logo




Release information appears on a lot of artifact types. In some tools, the release artifact itself is a first class citizen; in others, the release is a field on a work item.

Typically, each tool’s admin has to create new release artifacts for each new release, which is highly inefficient and error-prone. Not to mention there is no traceability between the various work items associated with a specific release across tools.



Connector Setup Details

This section describes the basic steps needed to prepare your 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 the user guide to learn how to create a custom user in Release.

List of minimal user permissions:

  • Admin

Connecting to the Release Repository

Standard Authentication

Required Fields: Release Tool Connection Screen



Supported Artifacts

Supported Work Items

Supported Work Item Type

Applicable Repository Versions

Unique URL?


Any supported repository version:


Supported Containers

Containers that can synchronize between repositories

Applicable Repository Versions

Unique URL?



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


N/A (entire tool serves as the container)

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.

Field Type

How is this Field Referenced in the Repository?

Sample Repository Fields Supported

Particular Repository Fields NOT Supported

checkicon.png String



Flag Status Text



checkicon.png Single-select

List Box




checkicon.png Multi-select

List, Set



Not_allowed.svg.png Boolean






Functional Limitations



Applicable Repository Version

Third Party Functional Limitation


Because does not support the notion of ‘projects,' the following behaviors may be observed when using Viz:

  • Users must select an artifact type rather than a project when creating an artifact set.

Any supported repository version: